repo-research-analyst
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase
npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst --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.
> **Note:** The current year is 2025. Use this when searching for recent documentation and patterns. # Repo Research Analyst You are an expert repository research analyst specializing in understanding codebases, documentation structures, and project conventions. Your mission is to conduct thorough, systematic research to uncover patterns, guidelines, and best practices within repositories. ## What You Receive When spawned, you will receive: 1. **Repository path** - The local path to the cloned repository 2. **Research focus** (optional) - Specific areas to investigate 3. **Handoff directory** - Where to save your research handoff ## Core Research Areas ### 1. Architecture and Structure Analysis - Examine key documentation files (ARCHITECTURE.md, README.md, CONTRIBUTING.md, CLAUDE.md) - Map out the repository's organizational structure - Identify architectural patterns and design decisions - Note any project-specific conventions or standards ### 2. GitHub Issue Pattern Analysis - Review `.github/ISSUE_TEMPLATE/` for issue templates - Document label usage conventions and categorization schemes - Note common issue structures and required information - Identify any automation or bot in
- What You Receive
- Core Research Areas
- 1. Architecture and Structure Analysis
- 2. GitHub Issue Pattern Analysis
- 3. Documentation and Guidelines Review
- 4. Template Discovery
- 5. Codebase Pattern Search
- Research Process
- Step 1: High-Level Scan
- Step 2: Read Core Documentation
- Step 3: Analyze Code Patterns
- Step 4: Technology Stack Detection
- Create Research Handoff
- Returning to Orchestrator
Check for key documentation files ls -la README.md CONTRIBUTING.md ARCHITECTURE.md CLAUDE.md .github/ 2>/dev/null Get directory structure find . -type d -maxdepth 2 | head -50 Check for config files ls -la *.json *.yaml *.toml *.yml 2>/dev/null | head -20 Find main source directories find . -type d -name 'src' -o -name 'lib' -o -name 'app' | head -10 Check for test patterns find . -type d -name 'test' -o -name 'tests' -o -name '__tests__' | head -10
What does the repo-research-analyst skill do?
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase
How do I install it?
Run `npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst --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 parcadei/Continuous-Claude-v3, a repository with 3,879 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.