Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
SkillScore61Maintained
Automatic
◆Coding pack
Last verified 8/27/2026
What it changes
Passed 10 of 16 test cases with the skill, and 5 of 16 without it.
Without skill30%
With skill61%
Checks it passed that the model alone missed
Starts by running gitnexus_rename with dry_run set to true.
Recommends calling gitnexus_context to identify all callees.
Recommends calling gitnexus_context with the target handler symbol.
and 9 more in the full report
10 fixed4 passed either way6 still failing3 broke
Pass-rate lift
+30 pp
Tokens
-5%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/27/2026v114 of 23 cases passed with skill · 16 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
We are attempting to run structural symbol analysis on our TypeScript project, but the underlying code index reports 'Index is stale'. What specific terminal command should we execute to refresh the index?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends executing npx gitnexus analyze in the terminal to re-index the repository.
Missed
Passed
case-04 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md116 linessingle file
Refactoring with GitNexus
When to Use
"Rename this function safely"
"Extract this into a module"
"Split this service"
"Move this to a new file"
Any task involving renaming, extracting, splitting, or restructuring code
Workflow
1. gitnexus_impact({target: "X", direction: "upstream"}) → Map all dependents
2. gitnexus_query({query: "X"}) → Find execution flows involving X
3. gitnexus_context({name: "X"}) → See all incoming/outgoing refs
4. Plan update order: interfaces → implementations → callers → tests
If "Index is stale" → run npx gitnexus analyze in terminal.
Checklists
Rename Symbol
- [ ] gitnexus_rename({symbol_name: "oldName", new_name: "newName", dry_run: true}) — preview all edits
- [ ] Review graph edits (high confidence) and ast_search edits (review carefully)
- [ ] If satisfied: gitnexus_rename({..., dry_run: false}) — apply edits
- [ ] gitnexus_detect_changes() — verify only expected files changed
- [ ] Run tests for affected processes
Extract Module
- [ ] gitnexus_context({name: target}) — see all incoming/outgoing refs
- [ ] gitnexus_impact({target, direction: "upstream"}) — find all external callers
- [ ] Define new module interface
- [ ] Extract code, update imports
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.