From development-skills
Traces code execution paths with file:line references and lightweight text diagrams of method flows. Verifies understanding before bug fixes, features, refactoring, TDD, or debugging.
npx claudepluginhub ntcoding/claude-skillz --plugin fetching-circleci-logsThis skill uses the workspace's default tool permissions.
Quick understanding before implementation - **just enough to guide TDD, no more**.
Traces code execution paths, data flows, and call graphs via /sourceatlas:flow queries. Reveals boundaries, entry points, cycles for understanding features and implementations.
Traces feature, request, or data flows through codebase from entry points (API routes, UI handlers, jobs) to storage, documenting layers, transformations, side effects, and dependencies via graphs or grep.
Investigates codebases using Claude-only tools to trace execution paths, understand architecture, and diagnose issues. Outputs analysis report with findings.
Share bugs, ideas, or general feedback.
Quick understanding before implementation - just enough to guide TDD, no more.
Before creating implementation plans, fix plans, or TDD cycles for bugs/features.
Answer these:
Simple class.method() flow with relevant data:
Event: EventName
↓ (contains: relevant fields)
Class.method() [file:line]
↓ (what it does)
Class.method() [file:line] ← 💥 Error here
↓
Result: What happens
Keep it short - 5-10 lines max.
Ask: "Here's the flow: [diagram]. Correct?"
Wait for confirmation, then proceed.
Problem: Email validation failing
Event: user.email.updated
↓ (email: "invalid@")
UpdateUserEmailHandler.execute() [line 281]
↓ (validates email format)
EmailValidator.parse() [line 289] ← 💥 Throws ValidationError
↓
Result: Error response
Current: Throws
Should: Use safeParse(), return validation error
❌ WRONG: "I'll fix the validation. Here's my plan..." ✅ RIGHT: "Let me trace where the error occurs... [diagram]. Correct?"