repo-scanning
Scan and document repository structure, patterns, and key components. Use when starting work on unfamiliar codebases.
Profile →npx skills add majiayu000/claude-skill-registry --skill repo-scanning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Repository Scanning Produce a comprehensive map of the repository to enable effective navigation and understanding. ## Process 1. Identify major directories and their purposes 2. Find key modules, services, or packages 3. Note conventions and patterns in use 4. Document entry points and important files 5. Flag any unusual structures or concerns ## Output Create `context/repo-map.md` using the template in `templates/repo-map.md`. ## Tips - Focus on structure, not implementation details - Note naming conventions observed - Identify test directories and their organization - Look for configuration files that reveal project setup
- Process
- Output
- Tips
What does the repo-scanning skill do?
Scan and document repository structure, patterns, and key components. Use when starting work on unfamiliar codebases.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill repo-scanning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.