repo-research-analyst_skill

This skill conducts comprehensive repository research, analyzing architecture, guidelines, templates, and patterns to reveal conventions and best practices.

Python

24

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ratacat/claude-skills --skill repo-research-analyst

SKILL.md5.2 KB

Overview

This skill performs systematic research of a code repository to uncover structure, conventions, and patterns developers should follow. It inspects architecture files, contribution guidelines, issue templates, and code patterns to produce an actionable summary suitable for contributors and maintainers. The output highlights authoritative rules, observed conventions, and gaps that need clarification.

How this skill works

I start by locating high-level docs (README.md, ARCHITECTURE.md, CONTRIBUTING.md, CLAUDE.md) to establish context, then map the repository layout and technology stack. I analyze issue history and labels to identify triage patterns, examine .github templates for required fields, and search the codebase with syntax-aware or text tools to surface implementation and naming conventions. Findings are cross-referenced and dated so you can trust which items are official guidelines versus inferred patterns.

When to use it

Before making your first contribution to learn repository expectations and workflow.
When preparing a clear, compliant issue or pull request to match project templates.
To audit documentation completeness and identify missing contribution guidance.
When onboarding a new team member who needs a quick orientation to repo conventions.
To prepare automated tooling (linters, CI jobs) aligned with project patterns.

Best practices

Prioritize official files (CONTRIBUTING.md, CLAUDE.md) and cite them in your work.
Follow discovered issue/PR templates and required metadata to avoid delays.
Use the same naming conventions and module layout identified in the codebase.
Cross-check recommendations across docs and recent commits to validate currency.
Call out contradictions in the repository and propose precise documentation fixes.

Example use cases

Map the repository structure and list core packages, entry points, and scripts.
Extract issue label taxonomy and example templates to standardize triage.
Produce a checklist for contributors: tests required, code style, and review steps.
Search for recurring implementation patterns (factory usage, plugin hooks, decorators).
Identify automation mentioned in docs (bots, CI workflows) and their triggers.

FAQ

I prioritize explicit documentation and CLAUDE.md instructions first; observed patterns are labeled as inferred and supported with file paths and examples.

Which tools do you use to search code patterns?

I prefer AST-aware searches when available, falling back to ripgrep-style text searches; results include exact file locations and examples.