Skill

repo-recap

Generate a concise recap of recent repository activity — commits, PRs merged, issues closed, and open blockers. Use for standups, sprint reviews, or onboarding new contributors.

npx claudepluginhub nassimbf/ftitos-claude-code

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Turn raw git history and issue tracker data into a readable activity summary.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars2

Forks0

Last CommitMay 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Repo Recap

Turn raw git history and issue tracker data into a readable activity summary.

When to Use

Daily standup prep — what shipped since yesterday?
Sprint review — what was completed this sprint?
Onboarding a new contributor — what's been happening?
Weekly status report for stakeholders

Process

1. Gather Activity Data

# Commits in the last 7 days
git log --oneline --since="7 days ago"

# PRs merged (GitHub CLI)
gh pr list --state merged --limit 20

# Issues closed
gh issue list --state closed --limit 20

# Open PRs (in review)
gh pr list --state open

2. Summarize by Category

Organize findings into:

Shipped (merged to main)

List features, fixes, and improvements with PR numbers
Group by area (frontend, backend, infra, docs)

In Progress (open PRs)

What's actively being reviewed or worked on
Flag anything blocked or stale

Issues Closed

Bugs fixed, features delivered, tasks completed

Open Issues (priority)

Critical and high severity items still open
Anything blocking the next release

3. Identify Patterns

After summarizing, call out:

Velocity: more or fewer commits than last period?
Hotspots: which files/areas changed most?
Blockers: anything open > 7 days that should be closed?
Test coverage trend: improving or degrading?

4. Format the Recap

## Repo Recap — [date range]

### Shipped
- [feat] Description (#PR)
- [fix] Description (#PR)

### In Progress
- [description] — assigned to [owner], opened [N] days ago

### Issues Closed
- [N] bugs, [N] features, [N] chores

### Open Blockers
- [issue title] — [severity], open [N] days

### Notes
[Any patterns, risks, or callouts]

Checklist

Git log pulled for the time window
PRs merged listed with summaries
Issues closed counted and categorized
Open blockers identified
Patterns and velocity noted
Recap written in standard format