plugins/cartograph/skills/call-chain/SKILL.md
Traces execution paths through the code graph with criticality scoring and Mermaid charts. Use when understanding how a function propagates through the system.
npx skillsauth add athola/claude-night-market call-chainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Trace execution flows through the codebase using the code knowledge graph.
This skill requires the gauntlet plugin for graph data. Discover it:
GRAPH_QUERY=$(find ~/.claude/plugins -name "graph_query.py" -path "*/gauntlet/*" 2>/dev/null | head -1)
If gauntlet is not installed: Fall back to static
analysis. Use grep to trace function calls and build
a Mermaid diagram manually from import/call patterns.
Skip graph-specific steps.
If installed but no graph.db: Tell the user to run
/gauntlet-graph build.
Accept target: Get a function name or entry point from the user (or trace all entry points).
Run flow tracing (requires gauntlet):
python3 "$GRAPH_QUERY" --action flows --depth 15
To filter by entry point:
python3 "$GRAPH_QUERY" --action flows --entry "main"
Fallback (no gauntlet): Trace calls with rg (or grep):
# Prefer rg (ripgrep) for speed; fall back to grep
if command -v rg &>/dev/null; then
rg -n "function_name\(" --type py . | head -20
else
grep -rn "function_name(" --include="*.py" . | head -20
fi
Build the call tree manually from search results.
Display as indented tree:
main() [criticality: 0.72]
-> validate_input()
-> parse_config()
-> process_data()
-> db.execute_query()
-> cache.store()
-> send_response()
Generate Mermaid flowchart:
flowchart LR
main --> validate_input
main --> process_data
main --> send_response
validate_input --> parse_config
process_data --> db.execute_query
process_data --> cache.store
Show criticality breakdown:
| Factor | Weight | Meaning | |--------|--------|---------| | File spread | 0.30 | Touches many files | | Security | 0.25 | Contains auth/crypto code | | External calls | 0.20 | Unresolved dependencies | | Test gap | 0.15 | Untested nodes in flow | | Depth | 0.10 | Deep call chains |
tools
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
testing
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
development
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
testing
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.