codebase-navigatorlisted

# Codebase Navigator A token-efficient skill for exploring any codebase quickly. The core principle: **one `bash_tool` call to map, then targeted `view` calls only on confirmed files.** --- This skill's approach: 1. **One `bash_tool` call** builds the full structural map (paths only, no content) 2. **Classify** the structure (monorepo? framework? lang?) 3. **Read only confirmed key files** — entry points, configs, the specific file asked for --- ## Step 1 — One-Shot Structure Scan Always start with this single bash command. Adjust `ROOT` to the user's project root (default: `.` or whatever path they gave). ```bash find ROOT -maxdepth 4 \ -not -path '*/node_modules/*' \ -not -path '*/.git/*' \ -not -path '*/dist/*' \ -not -path '*/build/*' \ -not -path '*/__pycache__/*' \ -not -path '*/.next/*' \ -not -path '*/coverage/*' \ -not -path '*/vendor/*' \ -not -path '*/venv/*' \ -not -path '*/.venv/*' \ | sort ``` <!-- **If the tree is very large (>300 lines):** Re-run with `-maxdepth 3`, or add `-type f` to show only files, or narrow to a subtree. --> --- ## Step 2 — Classify the Repo From the path list, identify: | Signal | Inference | |---|---| | `package.json` at root | Node/JS project | | `packages/` or `apps/` dirs | Monorepo (Turborepo, Nx, Lerna) | | `pyproject.toml` / `setup.py` | Python project | | `go.mod` | Go module | | `Cargo.toml` | Rust | | `next.config.*` | Next.js | | `vite.config.*` | Vite frontend | | `manage.py` | Django | | `ap