gjczone

MUST invoke BEFORE reading, editing, searching, or understanding ANY code in a project. pi-shazam builds a codebase graph (tree-sitter AST -> symbols -> dependencies -> PageRank) with 7 tools for query, verification, and safe code modification.

User-invoked surgical codebase inspection. Invoke when the user says 'how does this project implement X', 'find how Y works in this codebase', 'what patterns does this repo use', 'inspect this codebase for Z', 'trace the call chain of', or 'analyze the architecture of this project'. Also invoke proactively when entering an unfamiliar repository — if .inspect/ exists, read it directly; if not, offer to run repo-inspect. This skill uses a Rust binary (scripts/repo-inspect) to surgically extract relevant code instead of dumping the entire repo. The binary runs locally, respecting .gitignore, with zero API calls. Output is written to .inspect/ (gitignored). Do NOT invoke for general code review (use code-review skill), documentation generation (use project-init), or TDD (use test-driven-development).

MUST invoke this skill for ANY task that touches code — before reading, editing, searching, debugging, refactoring, navigating, understanding, deleting, renaming, or moving code. Before every grep, every find, every file read, every edit, every symbol lookup, every impact check, every dependency question. After every edit for verification. Also invoke for: investigating bugs, planning features, reviewing PRs, assessing dead code, mapping API routes, tracing call chains, checking diagnostics, auditing state machines. The only exceptions: single-character typo fixes, pure prose/doc edits with zero code impact, and purely non-coding conversations. When in doubt whether to invoke, invoke it.