From code-index
Code review workflow using dependency tracing to assess PR risk and coverage
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-index:reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the knowledge graph to assess PR risk, find hidden side effects, and verify test coverage.
Use the knowledge graph to assess PR risk, find hidden side effects, and verify test coverage.
Map changes to symbols:
diff_analysis(diff_spec="main")
For each high-impact symbol, trace dependencies:
trace_dependencies(target="OrderService", dependents=true)
Check module boundaries:
explore_structure()
Changes crossing module boundaries deserve extra scrutiny.
Verify test coverage -- for each affected flow:
trace_dependencies(target="OrderService", dependents=true, include_tests=true)
Before renaming a symbol:
# Preview all locations that would change
rename(symbol_name="oldName", new_name="newName", dry_run=true)
# Cross-reference with dependency trace
trace_dependencies(target="oldName", dependents=true)
npx claudepluginhub nnourr/code-indexCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.