← ClaudeAtlas

repo-onboardinglisted

Build and maintain a persistent, commit-tracked structural map of any codebase in .claude/repo-map/ and answer codebase questions using verified file:line evidence. Use when the user asks how something works in this codebase, where to make a change, for an architecture overview, or when onboarding to an unfamiliar repo.
tanhank/repo-onboarding · ★ 1 · Code & Development · score 74
Install: claude install-skill tanhank/repo-onboarding
# repo-onboarding Give the agent an accurate, persistent mental map of any codebase stored under `.claude/repo-map/` (`architecture.md`, `modules.md`, `entry-points.md`, `conventions.md`, and `index.json`), updating incrementally via Git commit diffs and grounding every architectural or code-level answer in verified `file:line` references. ## When to Use - Use when onboarding to an unfamiliar repository or when the user asks for an architecture overview, tour, or module breakdown. - Use when the user asks "how does X work here?", "where is Y implemented?", or "what calls Z?". - Use when the user asks "where do I change Y?" or "how do I add a new route, command, job, or test?" so changes follow the repository's real conventions. - Use when `.claude/repo-map/` already exists and needs an incremental refresh after new commits before answering structural questions. ## Steps ### Step 1: Check Existing Map State and Git Freshness Determine whether `.claude/repo-map/index.json` exists and whether its recorded commit matches the current Git `HEAD`. 1. Run the incremental diff checker from the skill directory against the target repository root: ```bash ./scripts/diff-check.sh --from-index <repo-root> ``` 2. Branch based on the reported `STATUS`: - **`FULL_SCAN_NEEDED` or `NO_GIT_REPO`**: Proceed to **Step 2 (Full Structural Scan)** to build `.claude/repo-map/` from scratch. - **`UP_TO_DATE`**: Skip rescanning and proceed directly to **Step 5 (Answer Questions Using the Map a