From idea-to-code
Locates production code definitions and usage sites (instantiations, calls, method invocations) for classes, functions, and methods. Use for 'where is X defined/called/instantiated?' queries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/idea-to-code:find-usageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find all production code locations where the specified class, function, or method is defined and used.
Find all production code locations where the specified class, function, or method is defined and used.
Definition — show where it is defined (file, line, containing class/module)
Usage sites — show where it is used in production code
For classes, complete ALL of: 2a. Instantiation sites — search for constructor calls 2b. Method invocation sites — read the class to find its public methods, then search for call sites of EACH method
For functions/methods: 2a. Call sites — search for all calls to the function/method
Exclude test code. Use a separate table per category:
| Location | Class/Function |
|---|---|
file.py:line | ClassName |
| Location | Class/Function | Context |
|---|---|---|
file.py:line | ClassName() | containing_function() |
| Location | Class/Function | Method |
|---|---|---|
file.py:line | ClassName | method_name() |
For top-level functions, put the function name in Class/Function and note "(top-level)" in Context.
After presenting the tables, read the surrounding context of each call site and identify cross-cutting patterns worth calling out. Examples:
Present findings as a short numbered list with file references.
npx claudepluginhub humansintheloop-dev/humansintheloop-dev-workflow-and-tools --plugin idea-to-codeTraces symbol usages across a codebase, builds call hierarchies, and groups references by type (definition, import, usage). Requires grepika MCP server.
Find symbol definitions by name regex, trace call sites with FQN, get symbol file locations, and explore class public APIs using Brokk's searchSymbols, scanUsages, getSymbolLocations, and getClassSkeletons tools.
Search code symbols (functions, classes, methods, types), find call sites and references, list file symbols, get outlines, check index status, and query static analysis findings. Requires indexed codebase.