
Repository Analyzer
Generates comprehensive markdown documentation of any codebase by scanning directory structure, detecting languages and frameworks, mapping dependencies, identifying architecture patterns, and flagging technical debt like TODOs and FIXMEs. Best for onboarding to unfamiliar projects or creating reference docs you can revisit later. It replaces hours of manual exploration with a single command that produces a structured report covering everything from lines of code and outdated packages to cyclomatic complexity and common entry points. Skip it if you just need to find specific code or get quick answers without the full writeup.
- skills.sh installs
- 241
- GitHub stars
- 16
- last updated
- Jun 3, 2026
Install
$ npx -y skills add jackspace/claudeskillz --skill repository-analyzer --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
# Use filesystem tools to map structure
tree -L 3 -I 'node_modules|.git|dist|build'
Step 2: Count files by type
# 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...
Sponsors
Details
- Repository
- github.com/jackspace/claudeskillz
- First seen
- Jun 3, 2026