repo-research-analyst

Analyze repository documentation, structure, templates, and code patterns for architectural insights.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill repo-research-analyst-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-research-analyst
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/repo-research-analyst
Command: npx skills add https://github.com/jikig-ai/soleur --skill repo-research-analyst-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and maintainers rapidly discover and understand a repository's architecture, documentation, contribution rules, issue patterns, and implementation conventions so onboarding, audits, and design decisions are faster and less error-prone.

Core Features & Use Cases

  • Repository Mapping: Locate and summarize key files such as README.md, ARCHITECTURE.md, CONTRIBUTING.md, and repository metadata to reveal project intent and structure.
  • Issue & Template Analysis: Identify issue and PR template formats, label taxonomies, and common issue structures to standardize reporting and triage.
  • Code & Pattern Discovery: Use syntax-aware searches (ast-grep) or text searches (ripgrep) to surface naming conventions, repeated implementations, and architectural patterns across the codebase.
  • Use Case: When preparing contributor documentation or performing an architecture review, run this Skill to produce a structured Repository Research Summary with file paths, examples, and recommendations.

Quick Start

Use the repo-research-analyst skill to generate a Repository Research Summary that maps architecture files, contribution guidelines, issue templates, and common code patterns for the current project.

Frequently Asked Questions about repo-research-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a GitHub repository structure for onboarding?

Analyzing a GitHub repository structure involves mapping key documentation files, directory layouts, and .github templates to reveal project intent and contribution rules. This skill summarizes README, CONTRIBUTING, and architecture files to produce a structured research summary for onboarding.

What's the best way to discover code patterns and naming conventions in a codebase?

The best way to discover code patterns is using syntax-aware searches via ast-grep or text searches with ripgrep. This skill applies these tools to surface naming conventions, repeated implementations, and architectural patterns across the codebase.

Can I identify issue and PR template formats to standardize contributor reporting?

You can identify issue and PR template formats by extracting template fields, label taxonomies, and common issue structures. This skill analyzes .github templates to standardize reporting and triage by documenting label usage and structural formats.

Does repository research work with ripgrep and ast-grep for codebase analysis?

Repository research works with ripgrep and ast-grep by leveraging syntax-aware searches and text matching for codebase analysis. This skill uses ast-grep when available and ripgrep for text search to report file paths, timestamps, and representative code examples.

When do I need to map repository architecture and contribution guidelines?

You need to map repository architecture and contribution guidelines when performing architecture reviews, preparing contributor documentation, or auditing a codebase. This skill extracts conventions and architectural decisions to reduce onboarding errors and streamline audits.