skills.rest
seabbs
seabbsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

repo-summary

Analyze GitHub repositories to generate structured markdown reports with activity metrics and code insights.

7|3|Updated Jul 31, 2025
Search Tags:#github#metrics#repository#reporting#analyze#code-churn
One-click install
npx skills add https://github.com/seabbs/claude-code-config --skill repo-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-summary
Source: https://github.com/seabbs/claude-code-config/tree/main/skills/repo-summary
Command: npx skills add https://github.com/seabbs/claude-code-config --skill repo-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a GitHub repository by combining activity metrics with code development insights to identify trends, hotspots, and growth areas.

Core Features & Use Cases

  • Activity profiling: Track commit frequency, churn, and contributor patterns over time.
  • Code-health insights: Identify hotspots, refactoring signals, and test coverage evolution.
  • Executive report: Generate a concise summary report suitable for stakeholders.

Quick Start

Run the repo-summary on a target repository to generate the combined activity and code-development insights report.

Frequently Asked Questions about repo-summary

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

FAQPage Schema
How do I analyze a GitHub repository to generate a markdown report of activity metrics?▼

To analyze a GitHub repository and generate a markdown report, run the repo-summary tool on your target repository to automatically combine commit frequency, code churn, and contributor metrics into a structured summary of trends and hotspots.

What GitHub metrics can I track to identify code churn and hotspots?▼

You can track GitHub metrics like commit frequency, code churn, and contributor patterns over time to identify hotspots and refactoring signals, which are aggregated into a concise executive report suitable for stakeholders.

Can I analyze private GitHub repositories or do they need to be public?▼

You can analyze private GitHub repositories as well as public ones, including remote repositories and local clones across organizations and forks, to produce combined activity metrics and code development insights.

What is the best way to get code-health insights and test coverage evolution from git history?▼

The best way to get code-health insights from git history is using a tool that performs git-history analysis to identify refactoring signals and track test coverage evolution alongside activity profiling to generate a comprehensive development report.

Does repo-summary work with repositories across different organizations and forks?▼

Yes, repo-summary works with repositories across organizations and forks, applying git-history analysis to public or private repositories whether accessed remotely or via a local clone during ongoing development and releases.

Are there limitations when analyzing ongoing development and releases in a GitHub repository?▼

The tool aggregates GitHub data and performs git-history analysis on ongoing development and releases, but it focuses on producing a concise summary report of metrics and trends rather than providing deep, granular code-level refactoring instructions.

Related Skills

Explore More Software Engineering Skills→
afel6afel6

github-auth

Configure GitHub authentication for git or gh CLI access.

Community
Intermediate
cy-walicy-wali

people-report

Generate headcount, attrition, diversity, and org health reports from HR data.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack-openclaw-retro

Generate weekly engineering retrospectives from git commit history and contributor patterns.

Community
Advanced
Community-AccessCommunity-Access
387

Analytics & Insights

Generate markdown and HTML GitHub analytics reports from pull request and issue metrics.

Official
Advanced