Individual skill

how

Trace how a subsystem works using code and runtime evidence. Use for architecture walkthroughs, data flow, call paths, and are-we-sure investigations.

skills/how/SKILL.md

Read pinned source

Source commit 79595c97d47b5400034fb985e67f1a00389a81af

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 22
Repository last updated: Nov 1, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
claude-code Repository topic
codex Repository topic
coding-agents Repository topic
cursor Repository topic
pstack Repository topic
cline Repository topic
copilot Repository topic
gemini Repository topic
engineering Derived category
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 958 bytes

Read excerpt

# How

Build an evidence-backed explanation of how the requested subsystem works.

1. Find the public/consumer entry point, then trace data and control flow toward the effect. Do not start from filenames guessed by name alone.
2. Read the core types and state ownership before narrating individual functions.
3. Use `vcs`, tests, or `observe` when they resolve an ambiguity. If `delegate` exists, split independent exploration areas and reconcile them yourself.
4. Draw a compact text or Mermaid diagram when it reduces reader load.
5. Test at least one claim that could easily be wrong by running or inspecting the real path.
6. Explain in consumer order: trigger -> boundary -> state/transform -> side effect -> observable result. Name file/symbol evidence and uncertainty.