Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/28/2026
What it changes
Passed 16 of 19 test cases with the skill, and 8 of 19 without it.
Without skill41%
With skill86%
Checks it passed that the model alone missed
Evaluates the risk level as MEDIUM.
Classifies depth 1 items as WILL BREAK.
Classifies depth 2 items as LIKELY AFFECTED.
and 9 more in the full report
10 fixed9 passed either way3 still failing0 broke
Pass-rate lift
+45 pp
Tokens
-16%
Agent turns
0%
Response time
-73%
Model gemini-3.6-flashMeasured 8/28/2026v119 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
During blast radius inspection of `sendNotification`, symbols appear at depth d=3 in the dependency graph. What risk status label corresponds to depth 3 items?
What was checked, without and with the skill
Checked
Without skill
With skill
Classifies depth 3 items as MAY NEED TESTING.
Missed
Passed
case-08 · gemini-3.6-flash · 8/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md92 linessingle file
Impact Analysis with GitNexus
When to Use
"Is it safe to change this function?"
"What will break if I modify X?"
"Show me the blast radius"
"Who uses this code?"
Before making non-trivial code changes
Before committing — to understand what your changes affect
Workflow
1. gitnexus_impact({target: "X", direction: "upstream"}) → What depends on this
2. READ gitnexus://repo/{name}/processes → Check affected execution flows
3. gitnexus_detect_changes() → Map current git changes to affected flows
4. Assess risk and report to user
If "Index is stale" → run npx gitnexus analyze in terminal.
Checklist
- [ ] gitnexus_impact({target, direction: "upstream"}) to find dependents
- [ ] Review d=1 items first (these WILL BREAK)
- [ ] Check high-confidence (>0.8) dependencies
- [ ] READ processes to check affected execution flows
- [ ] gitnexus_detect_changes() for pre-commit check
- [ ] Assess risk level and report to user
Lead-only council for a hard-to-reverse fork - a neutral brief, sealed independent seats, one premise verifier on unanimity, bounded verifiers, one cross-examination round, a draft-verdict audit, and one binding verdict recorded as a decision with its dissent. Never inside a seat.