From ferret
Use when tracing call flow, understanding what calls what, or following execution paths through a codebase. Use after ferret search has identified the key symbols involved.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ferret:graphThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to `ferret graph`, which shows what a function calls and what calls it.
You have access to ferret graph, which shows what a function calls and what calls it.
ferret graph src/auth/login.ts:validateToken
ferret graph src/auth/login.ts:validateToken --depth 3 # Deeper traversal (default: 2)
ferret graph -p /path/to/proj src/auth/login.ts:validateToken
Format: <file>:<SymbolName> or <file>:<Class>.<method>.
The graph uses simple name matching and is not always accurate. It can:
Treat graph output as a rough orientation, not a precise call graph. Always verify interesting edges by reading the actual source code.
Graph output shows calls: and called by: edges. Use these to guide where to look next, then confirm by reading the referenced files directly.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub taiters/ferret --plugin ferret