repository-analyzer
Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.
npx skills add majiayu000/claude-skill-registry --skill repository-analyzer-jackspace-claudeskillz-17c1e6ca --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 Analyzer ## Purpose Quickly understand unfamiliar codebases by automatically scanning structure, detecting technologies, mapping dependencies, and generating comprehensive documentation. **For SDAM users**: Creates external documentation of codebase structure you can reference later. **For ADHD users**: Instant overview without manual exploration - saves hours of context-switching. **For all users**: Onboard to new projects in minutes instead of days. ## Activation Triggers - User says: "analyze repository", "understand codebase", "document project" - Requests for: "what's in this repo", "how does this work", "codebase overview" - New project onboarding scenarios - Technical debt assessment requests ## Core Workflow ### 1. Scan Repository Structure **Step 1: Get directory structure** ```bash # Use filesystem tools to map structure tree -L 3 -I 'node_modules|.git|dist|build' ``` **Step 2: Count files by type** ```bash # Identify languages used find . -type f -name "*.js" | wc -l find . -type f -name "*.py" | wc -l find . -type f -name "*.go" | wc -l # etc... ``` **Step 3: Measure codebase size** ```bash # Count lines of code cloc . --exclude-dir=node_modules,.git,dist,b
- Purpose
- Activation Triggers
- Core Workflow
- 1. Scan Repository Structure
- 2. Detect Technologies
- 3. Map Dependencies
- 4. Identify Architecture Patterns
- 5. Extract Technical Debt
- 6. Generate Documentation
- Advanced Analysis Features
- Git History Analysis
- Code Complexity Metrics
- Dependency Security
- Integration with Other Skills
Use filesystem tools to map structure tree -L 3 -I 'node_modules|.git|dist|build' Identify languages used find . -type f -name "*.js" | wc -l find . -type f -name "*.py" | wc -l find . -type f -name "*.go" | wc -l etc... Count lines of code cloc . --exclude-dir=node_modules,.git,dist,build Read package.json
What does the repository-analyzer skill do?
Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill repository-analyzer-jackspace-claudeskillz-17c1e6ca --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.