repo-explorer

# Repo Explorer Launch a separate Claude Code CLI process (`claude -p`) with read-only tools to explore a repository and answer questions about it. Supports both local repositories and remote URLs. ## Workflow ### 1. Determine repo source, question, and model From the user's message extract: - **source**: one of: - **local path** (`~/projects/foo`, `/opt/services/bar`, `.` or omitted = cwd) - **remote URL** (`https://github.com/owner/repo`, `git@github.com:owner/repo.git`) - **shorthand** (`owner/repo` — treat as `https://github.com/owner/repo`) - **question**: what to find out about the repository. - **model** — pick by task type, not by habit: - **`haiku`** — mechanical lookup, where the answer is *located* in the code and just needs finding: "what endpoints exist", "where is X defined", "list the migrations", structure inventory, "does this repo use Y". - **`sonnet`** — analytical work, where the answer must be *judged*, not just found: "what can we learn/borrow from this repo", applicability assessment, design/architecture review, comparing approaches, security analysis, "what's original here", trade-off summaries. Cue words: оцени, что полезного, идеи, применимость, review, compare, learn from. - A cheap model on an analytical question produces shallow results with flattened nuances that cost more to verify than the tokens saved — this rule exists because it happened. - An explicit user request ("use haiku", "запусти sonnet", op...