SkillAgentSearch skills...

repo-research-analyst

Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase

Install / Use

npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Our assessment of repo-research-analyst

repo-research-analyst scores 86/100 on our quality scale, 706th of 1,153 Content & Media skills we index.

Its SKILL.md is 6.3 KB long, well organised into 47 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

With 3,943 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
15/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 10 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 94/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

repo-research-analyst compared with similar skills

All 4 of these similar skills score higher than repo-research-analyst; compare them before choosing.

SkillScoreStarsUpdatedFormat
repo-research-analyst (this skill)by parcadei863.9k10mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install repo-research-analyst?
Run npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst. The install tabs above show the steps for each supported agent.
Which AI agents does repo-research-analyst work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is repo-research-analyst safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 94/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is repo-research-analyst still maintained?
The repository was last updated about 10 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: repo-research-analyst description: Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase

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 interactions

3. Documentation and Guidelines Review

  • Locate and analyze all contribution guidelines
  • Check for issue/PR submission requirements
  • Document any coding standards or style guides
  • Note testing requirements and review processes

4. Template Discovery

  • Search for issue templates in .github/ISSUE_TEMPLATE/
  • Check for pull request templates (.github/PULL_REQUEST_TEMPLATE.md)
  • Document any other template files (e.g., RFC templates)
  • Analyze template structure and required fields

5. Codebase Pattern Search

  • Use Grep for text-based pattern searches
  • Identify common implementation patterns
  • Document naming conventions and code organization
  • Find example implementations to follow

Research Process

Step 1: High-Level Scan

# 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

Step 2: Read Core Documentation

Read these files completely if they exist:

  • README.md - Project overview
  • CONTRIBUTING.md - Contribution guidelines
  • ARCHITECTURE.md - Architecture decisions
  • CLAUDE.md - AI assistant instructions
  • .github/ISSUE_TEMPLATE/*.md - Issue templates
  • .github/PULL_REQUEST_TEMPLATE.md - PR template

Step 3: Analyze Code Patterns

# 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

# Look for config patterns
find . -name '*.config.*' -o -name 'config.*' | head -20

Step 4: Technology Stack Detection

  • Check package.json (Node.js/npm)
  • Check pyproject.toml or setup.py (Python)
  • Check Cargo.toml (Rust)
  • Check go.mod (Go)
  • Check Gemfile (Ruby)

Create Research Handoff

Write your findings to the handoff directory.

Handoff filename: repo-research-<repo-name>.md

---
date: [ISO timestamp]
type: repo-research
status: complete
repository: [repo name or path]
---

# Repository Research: [Repo Name]

## Overview
[1-2 sentence summary of what this project is]

## Architecture & Structure

### Project Organization
- [Key directories and their purposes]
- [Main entry points]

### Technology Stack
- **Language:** [Primary language]
- **Framework:** [Main framework if any]
- **Build Tool:** [Build/package manager]
- **Testing:** [Test framework]

### Key Files
- `path/to/important/file` - [Purpose]

## Conventions & Patterns

### Code Style
- [Naming conventions]
- [File organization patterns]
- [Import/module patterns]

### Implementation Patterns
- [Common patterns found with examples]
- [File: line references]

## Contribution Guidelines

### Issue Format
- [Template structure if found]
- [Required labels]
- [Expected information]

### PR Requirements
- [Review process]
- [Testing requirements]
- [Documentation requirements]

### Coding Standards
- [Linting rules]
- [Formatting requirements]
- [Type checking]

## Templates Found

| Template | Location | Purpose |
|----------|----------|---------|
| [Name] | [Path] | [What it's for] |

## Key Insights

### What Makes This Project Unique
- [Notable patterns or decisions]
- [Project-specific conventions]

### Gotchas / Important Notes
- [Things to watch out for]
- [Non-obvious requirements]

## Recommendations

### Before Contributing
1. [Step 1]
2. [Step 2]

### Patterns to Follow
- [Pattern with file reference]

## Sources
- [Files read with paths]

Returning to Orchestrator

After creating your handoff, return:

Repository Research Complete

Repository: [name]
Handoff: [path to handoff file]

Key Findings:
- Language/Stack: [tech stack]
- Structure: [brief structure note]
- Conventions: [key conventions]

Notable:
- [Most important insight 1]
- [Most important insight 2]

Ready for [planning/contribution/implementation].

Important Guidelines

DO:

  • Read documentation files completely
  • Note specific file paths and line numbers
  • Cross-reference patterns across the codebase
  • Distinguish official guidelines from observed patterns
  • Note documentation recency (last update dates)

DON'T:

  • Skip the handoff document
  • Make assumptions without evidence
  • Ignore project-specific instructions (CLAUDE.md)
  • Over-generalize from single examples

Search Strategies:

  • For code patterns: Grep with appropriate file type filters
  • For file discovery: Glob patterns
  • For structure: ls and find via Bash
  • Read files completely, don't sample

Example Invocation

Task(
  subagent_type="general-purpose",
  model="sonnet",
  prompt="""
  # Repo Research Analyst

  [This entire SKILL.md content]

  ---

  ## Your Context

  ### Repository Path:
  /path/to/cloned/repo

  ### Research Focus:
  [Optional: specific areas to investigate, e.g., "focus on API patterns"]

  ### Handoff Directory:
  thoughts/handoffs/<session>/

  ---

  Research the repository and create your handoff.
  """
)

Related Skills

View on GitHub
GitHub Stars3.9k
CategoryContent
Updated9mo ago
Forks303

Languages

Python

Trust signals

94/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low