repo-recap

Solid

Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).

AI & Automation 62,019 stars 3821 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
40
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Repo Recap Generate a structured recap of the repository state: open PRs, open issues, recent releases, and executive summary. Output is formatted as Markdown with clickable GitHub links, ready to share. ## Language - Check the argument passed to this skill - If `en` or `english` → produce the recap in English - If `fr`, `french`, or no argument → produce the recap in French (default) ## Preconditions Before gathering data, verify: ```bash # Must be inside a git repo git rev-parse --is-inside-work-tree # Must have gh CLI authenticated gh auth status ``` If either fails, stop and tell the user what's missing. ## Steps ### 1. Gather Data Run these commands in parallel via `gh` CLI: ```bash # Repo identity (for links) gh repo view --json nameWithOwner -q .nameWithOwner # Open PRs with metadata gh pr list --state open --limit 50 --json number,title,author,createdAt,changedFiles,additions,deletions,reviewDecision,isDraft # Open issues with metadata gh issue list --state open --limit 50 --json number,title,author,createdAt,labels,assignees # Recent releases (for version history) gh release list --limit 5 # Recently merged PRs (for contributor activity) gh pr list --state merged --limit 10 --json number,title,author,mergedAt ``` Note: `author` in JSON results is an object `{login: "..."}` — always extract `.author.login` when processing. ### 2. Determine Maintainers To distinguish "our PRs" from external contributions: ```bash gh api repos/{owner}/{repo}/collab...

Details

Author
rtk-ai
Repository
rtk-ai/rtk
Created
4 months ago
Last Updated
today
Language
Rust
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category