Repo Recap

Generate a structured repository status report including open pull requests, issues, and recent releases.

78.1k|4.9k|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/rtk-ai/rtk --skill repo-recap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Repo Recap
Source: https://github.com/rtk-ai/rtk/tree/main/.claude/skills/repo-recap
Command: npx skills add https://github.com/rtk-ai/rtk --skill repo-recap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the difficulty of maintaining visibility into repository health, helping teams quickly identify stalled pull requests, active issues, and recent release history without manual GitHub dashboard navigation.

Core Features & Use Cases

  • Automated Repository Triage: Automatically categorizes pull requests into 'Our PRs', 'External Reviewable', and 'External Problematic' based on size and CI status.
  • Executive Summary: Provides a high-level overview of contributor activity, risks, and quick wins to facilitate team meetings.
  • Use Case: Use this before a weekly sync to generate a ready-to-share Markdown report that highlights which PRs need immediate attention and which issues are currently in progress.

Quick Start

Run the repo-recap skill to generate a repository status report in English.

Frequently Asked Questions about Repo Recap

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

FAQPage Schema
How do I generate a repository recap?

Run the repo-recap skill to automatically fetch open PRs, issues, and releases from your current repository. The skill formats this data into a Markdown report and copies it to your clipboard.

What GitHub CLI permissions are required?

The skill requires the GitHub CLI (gh) to be authenticated with sufficient permissions to list PRs, issues, and repository collaborators. Ensure you have run 'gh auth login' before execution.

Can I generate the report in different languages?

Yes, the skill supports English and French. Pass 'en' or 'fr' as an argument to the skill to specify your preferred output language.

How does the skill categorize pull requests?

It categorizes PRs based on author status (collaborator vs. external), size (additions and file count), and CI status. It flags problematic PRs that have merge conflicts, failing checks, or excessive size.

What happens if there are no open PRs or issues?

The skill is designed to handle empty states gracefully by displaying a clear message such as 'No open PRs' or 'Aucune PR ouverte' instead of an empty table.