An AI agent skill for reverse-engineering and researching open-source projects. Ask "how is X implemented?" and get compact, structured output — no need to dump the entire codebase into context.
npx skills add https://github.com/gjczone/repo-inspect --skill repo-inspectrepo-inspect is a skill that gives AI agents surgical access to any codebase. Instead of reading thousands of irrelevant lines, the agent asks a focused question and gets exactly the relevant code — ranked, with line numbers and context.
| Command | When to use | What it does |
|---|---|---|
overview |
First time opening a repo | One-page project spine: languages, structure, key modules, entry points |
find-how |
"How is X implemented?" | Searches codebase, returns ranked files with matched lines ± context |
trace |
"What calls this function?" | Follows call chains — callers and callees of a symbol |
entries |
"Where does execution start?" | Detects entry points: CLI commands, HTTP routes, event handlers |
patterns |
"What design patterns are used?" | Heuristic detection of common patterns |
data |
"What data structures exist?" | Extracts type definitions, structs, interfaces, enums |
hotspots |
"What files change most often?" | Ranks files by git change frequency |
All output lands in .inspect/ — compact Markdown (default) or JSON.
# Reverse-engineer how auth works in any repo
repo-inspect --repo ./some-project find-how "authentication"
# Research a remote repo without cloning
repo-inspect --repo gjczone/repo-inspect overview
# Trace call chain of a function
repo-inspect --repo . trace "handle_request" --depth 3Inspect any public GitHub repository without cloning — just use owner/repo:
repo-inspect --repo rust-lang/rust find-how "async"Fetches file trees and raw files via GitHub API. Set GITHUB_TOKEN to avoid rate limits. Results cached locally for 24 hours.
Rust, Python, TypeScript, Go — with tree-sitter structured parsing. All other languages work via text-level search.
Built with tree-sitter for structured code parsing.