New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Repo Research Analyst

by parcadei in parcadei/Continuous-Claude-v3

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

MITAuto-check passedAgent Workflows

Install Repo Research Analyst

skills CLI
$ npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install parcadei/Continuous-Claude-v3 repo-research-analyst --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/repo-research-analyst .claude/skills/repo-research-analyst && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
repo-research-analyst
GitHub stars
3.9k
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
396 words
Files
1
Skills in repo
141
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 9 steps: Architecture and Structure Analysis → GitHub Issue Pattern Analysis → Documentation and Guidelines Review → …
  • Agent Workflows work in your project
  • SKILL.md covers What You Receive, Core Research Areas, Research Process and Create Research Handoff, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Repo Research Analyst is an agent skill from parcadei/Continuous-Claude-v3. Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. It works with GitHub. The repository describes itself as: Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/repo-research-analyst”

Requirements

  • Node.js

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Architecture and Structure Analysis
  2. GitHub Issue Pattern Analysis
  3. Documentation and Guidelines Review
  4. Template Discovery
  5. Codebase Pattern Search
  6. High-Level Scan
  7. Read Core Documentation
  8. Analyze Code Patterns
  9. Technology Stack Detection

What it can do on your machine

Read from SKILL.md and the folder at commit d07ff4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Repo Research Analyst loads about 1.6k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 396 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from parcadei/Continuous-Claude-v3 at commit d07ff4b, republished under its MIT licence (© parcadei). 396 words, ~1,625 tokens.

Download SKILL.mdSave it as .claude/skills/repo-research-analyst/SKILL.md (or your agent's skills folder).
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
  • 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
bash
# 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
Show full SKILL.md (157 more words)Show less
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
bash
# 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

markdown
---
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.
  """
)

© parcadei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/repo-research-analyst of parcadei/Continuous-Claude-v3.

Open the folder on GitHubat commit d07ff4b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in parcadei/Continuous-Claude-v3, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Repo Research Analyst next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Repo Research Analyst compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Repo Research Analyst this skillparcadei/Continuous-Claude-v33.9k1 repos~1.6kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Auto Skill Buildertradecatlabs/vibe-coding-cn17k1 repos~2.4kAutomated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Skill Seekers Builderyusufkaraaslan/Skill_Seekers15k—~760Automated safety check: PassMIT
Repomix Codebase Packeryamadashy/repomix29k—~1.3kAutomated safety check: NotesMIT

Similar skills

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • Auto Skill Builder

    tradecatlabs/vibe-coding-cn

    Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire.

    17k GitHub starsUsed in 1 repo~2.4k tokens
    Agent WorkflowsAuto-check passed

  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Skill Seekers Builder

    yusufkaraaslan/Skill_Seekers

    Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.

    15k GitHub stars~760 tokensUpdated 10 days ago
    Agent WorkflowsAuto-check passed

  • Repomix Codebase Packer

    yamadashy/repomix

    Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.

    29k GitHub stars~1.3k tokensUpdated today
    Agent WorkflowsAuto-check: notes

  • Context Mode Ops

    mksglu/context-mode

    Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.

    26k GitHub stars~6k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from parcadei/Continuous-Claude-v3

All 141 skills in this repo

  • Compound Learnings

    parcadei/Continuous-Claude-v3

    Transform session learnings into permanent capabilities (skills, rules, agents).

    3.9k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check: notes

  • Debug Hooks

    parcadei/Continuous-Claude-v3

    Systematic hook debugging workflow. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 1 repo~863 tokens
    Auto-check: notes

  • Tldr Deep

    parcadei/Continuous-Claude-v3

    Full 5-layer analysis of a specific function. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 1 repo~677 tokens
    Auto-check passed

  • Gradient Methods

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for gradient methods in optimization

    3.9k GitHub starsUsed in 2 repos~1k tokens
    Auto-check: notes

  • Math

    parcadei/Continuous-Claude-v3

    Unified math capabilities - computation, solving, and explanation.

    3.9k GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check: notes

  • Math Model Selector

    parcadei/Continuous-Claude-v3

    Routes problems to appropriate mathematical frameworks using expert heuristics

    3.9k GitHub starsUsed in 2 repos~841 tokens
    Auto-check passed

Works with

Categories

Questions about Repo Research Analyst

What does Repo Research Analyst do?

Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase. Repo Research Analyst is an agent skill from parcadei/Continuous-Claude-v3.

When should I use Repo Research Analyst?

Repo Research Analyst fits situations like: agent Workflows work in your project.

How do I install Repo Research Analyst in Claude Code?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst -a claude-code`. Or copy the skill folder (.claude/skills/repo-research-analyst in parcadei/Continuous-Claude-v3) into .claude/skills/repo-research-analyst in your project. Claude Code loads it when a task matches its description.

How do I install Repo Research Analyst in Codex?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst -a codex`. Or copy the skill folder (.claude/skills/repo-research-analyst in parcadei/Continuous-Claude-v3) into .agents/skills/repo-research-analyst in your project. Codex loads it when a task matches its description.

Can I use Repo Research Analyst in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add parcadei/Continuous-Claude-v3 --skill repo-research-analyst -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-research-analyst, .gemini/skills/repo-research-analyst, .github/skills/repo-research-analyst and .opencode/skills/repo-research-analyst in your project.

What does Repo Research Analyst need to run?

SKILL.md names no scripts, command-line tools or credentials: Repo Research Analyst is instructions for the agent only. Our summary lists: Node.js.

Does Repo Research Analyst access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Repo Research Analyst safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Repo Research Analyst use?

Repo Research Analyst is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Repo Research Analyst use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Repo Research Analyst?

Skills that share tags, products or a category with Repo Research Analyst: Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Auto Skill Builder (tradecatlabs/vibe-coding-cn, 17k stars), Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars) and Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Repo Research Analyst?

parcadei (a GitHub user) maintains it in parcadei/Continuous-Claude-v3, which has 3,943 GitHub stars. The repository holds 141 skills in this directory. The repository was last updated on January 26, 2026.

Source: parcadei/Continuous-Claude-v3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.