impact
Skill0 starsChanged 57 days agoApache-2.0View on GitHub
Use when you need the blast radius of a change — "who calls X", "what breaks if I touch Y", upstream/downstream dependents of a symbol or file. Opt-in graph-first: if the optional `graphify` knowledge graph is present and fresh, query it (deterministic, no-LLM, ~1000x fewer tokens than grep-and-read); otherwise fall back to ripgrep. Never required — degrades gracefully when graphify is absent.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- paulocsb/worldcup-fifa-pooltheir own version, first seen Nov 8, 2026
- ai-agent-lead/skillstheir own version, first seen Nov 1, 2026
- ShiftinBits/constellation-claudetheir own version, first seen Nov 1, 2026
- stoa-platform/stoatheir own version, first seen Nov 1, 2026
- DataWithBaraa/claude-code-data-engineering-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use debug and docs.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 4 projects that use this
Microsoft AzureSkilldocs
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- DataWithBaraa/claude-code-data-engineering-skills★ 84same name
- mbwsims/claude-universe★ 71same name
- Anuj7411/sipcode★ 46same name
- drafthq/draft★ 40same name
- huiruru/ecoguilt★ 9same name
- stoa-platform/stoa★ 9same name
- gonimar/claude-web-studio★ 4same name
- ai-agent-lead/skills★ 3same name
- jskswamy/skills★ 3same name
- Jsnnmsc/10000x-engineer★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architect-reviewSkill
- brainstormingSkill
- clean-codeSkill
- close-gold-gapSkill
- codebase-auditSkill
- configureSkill
- context-rot-managementSkill
- epic-decomposeSkill
- gold-auditSkill
- levelupSkill
- product-acceptanceSkill
- refutationSkill
- senior-surveySkill
- ssot-navigationSkill
- tabletopSkill
- tddSkill
- understand-codeSkill
- verificationSkill
- visual-verificationSkill
- wave-drainSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 70
Treat EXTRACTED edges (found in real code) as reliable.
- Distinctive: line 86
When graphify is unavailable or returns "not in graph" (a miss), use ripgrep — correct, just more tokens:
- Very specific: line 100
Optional, never fatal: No gate, plan, or /ship phase may _require_ graphify.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Impact (blast radius)
Goal: answer "what depends on X?" — the upstream/downstream blast radius of a symbol or file — accurately and cheaply, before you change it.
Opt-in, graph-first. arbiter does not require any graph tool. But if the optional
graphify knowledge graph is installed and a graphify-out/graph.json
exists in the repo, this skill queries the graph first — it is deterministic (no LLM),
pre-computes the dependency edges, and answers a blast-radius query in ~1000x fewer tokens than
loading every grep hit. When the graph is absent or the symbol is not in it, the skill falls
back to ripgrep. Either way you get an answer; the graph just makes it cheap and complete.
This is the analysis sibling of
/ship: run/impactto scope a change before planning, and in/ship's plan/red-team phases to validate that the plan touched everything the change actually reaches.
Step 0 — Detect availability (graceful)
command -v graphify >/dev/null 2>&1 && test -f graphify-out/graph.json- Available → continue with the graph path (Steps 1–3).
- Not available → skip to Fallback (ripgrep). Do NOT fail; graphify is optional. If the
user wants the cheap path, tell them once: install the
graphifyCLI (auv tool) and rungraphify update .to buildgraphify-out/.
Step 1 — Ensure the graph is fresh (deterministic, no-LLM)
The graph is a derived artifact; it is only trustworthy when it matches the working tree.
# Stale if the recorded build commit != HEAD, or tracked code changed in the working tree.
build_commit="$(sed -n 's/^build_commit: *//p' graphify-out/GRAPH_REPORT.md 2>/dev/null)"
head="$(git rev-parse HEAD)"
if [ "$build_commit" != "$head" ] || ! git diff --quiet; then
graphify update . # deterministic refresh; no model involved
fiRefreshing is cheap and never asks a model anything — it re-extracts edges from source.
Step 2 — Query the blast radius
graphify explain "<symbol>" --graph graphify-out/graph.json # upstream + downstream dependents
graphify path "<A>" "<B>" --graph graphify-out/graph.json # shortest dependency chain A→B- Treat
EXTRACTEDedges (found in real code) as reliable. - Flag
INFERREDedges (model-guessed at graph-build time) as "verify by hand" in any review/red-team note — do not trust them blindly.
Step 3 — Report
Summarize: the changed symbol/file, its direct dependents, the transitive reach
(modules/files), and any INFERRED edges that need manual confirmation. Feed this into the plan
(which files the change must touch) and the red-team (what it might have missed).
Fallback (ripgrep)
When graphify is unavailable or returns "not in graph" (a miss), use ripgrep — correct, just more tokens:
rg -n --no-heading -w "<symbol>" -g '!**/dist/**' -g '!**/node_modules/**'Then read the hits to separate definitions from call sites. This is the historical default and is always available; the graph is purely an optimization on top of it.
Hard rules
- Optional, never fatal. No gate, plan, or
/shipphase may require graphify. Absence ⇒ fall back, never error. - Deterministic graph only. Graph build/refresh (
graphify update) is no-LLM; never "guess" a blast radius and present it as graph output. - Freshness before trust. A stale graph is worse than none — always run Step 1 first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

