Help us improve
Share bugs, ideas, or general feedback.
From ed3d-research-agents
Investigates codebase to verify design assumptions, find patterns, locate features, confirm file locations/structure, and ground planning in reality before implementation.
npx claudepluginhub ed3dai/ed3d-plugins-testing --plugin ed3d-research-agentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/ed3d-research-agents:investigating-a-codebaseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Understand current codebase state to ground planning and design decisions in reality, not assumptions. Find existing patterns, verify design assumptions, and provide definitive answers about what exists and where.
Investigates codebase to verify design assumptions, find patterns, locate features, confirm file locations/structure, and ground planning in reality before implementation.
Maps codebase structure, patterns, symbols, and dependencies using ast-grep and bash scripts. Outputs factual maps with paths/line numbers to .artifacts/research/.
Explores project structure, configurations, code patterns, conventions, tests, and dependencies before modifying existing code to understand context and avoid bugs.
Share bugs, ideas, or general feedback.
Understand current codebase state to ground planning and design decisions in reality, not assumptions. Find existing patterns, verify design assumptions, and provide definitive answers about what exists and where.
Use for:
Don't use for:
When given design assumptions to verify:
Why this matters: Prevents implementation plans based on wrong assumptions about codebase structure.
| Task | Strategy |
|---|---|
| Where is X | Glob likely names → Grep keywords → Read matches |
| How does X work | Find entry point → Follow imports → Read implementation |
| What patterns exist | Find examples → Compare implementations → Extract conventions |
| Does X exist | Multiple searches → Definitive yes/no → Evidence |
| Verify assumptions | Extract claims → Search each → Compare reality vs expectation |
Multiple search approaches:
Don't stop at first result:
Verify everything:
Lead with direct answer:
Provide actionable intelligence:
Handle "not found" confidently:
| Mistake | Fix |
|---|---|
| Assuming file locations | Always verify with Read/Glob before reporting |
| Stopping at first result | Explore multiple paths to verify findings |
| Vague locations ("in auth folder") | Exact paths (src/auth/index.ts:42) |
| Not documenting search strategy | Explain what was checked when reporting "not found" |
| Confusing "not found" types | Distinguish "doesn't exist" from "couldn't locate" |
| Skipping design assumption comparison | Explicitly report: confirmed/discrepancy/addition/missing |
| Reporting assumptions as facts | Only report what was verified in codebase |