AI SummaryGenerate a markdown changelog from GitHub PRs for sprint review meetings. Both can be overridden if the user explicitly provides a different author or date. 1. Detect the current user (unless explicitly provided):
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "sprint-review" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/sprint-review && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/sprint-review/SKILL.md "https://raw.githubusercontent.com/rhesis-ai/rhesis/main/.cursor/skills/sprint-review/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Generate a sprint review changelog from GitHub pull requests. Lists PRs by a given author since a given date, groups them into Features and Fixes, and writes a markdown summary.
Features
Short heading One-to-two sentence description. • #<number> -- <title> • #<number> -- <title> (open/draft if not merged)
Sprint Review
Generate a markdown changelog from GitHub PRs for sprint review meetings.
Defaults
• Time range: last two weeks (14 days from today) • Author: the current GitHub user -- detect automatically via gh api user --jq .login Both can be overridden if the user explicitly provides a different author or date.
Workflow
• Detect the current user (unless explicitly provided): `bash gh api user --jq .login ` • Collect PRs using GitHub CLI (default: last 14 days): `bash gh pr list --author <username> --state all --search "created:>=<date>" --limit 100 \ --json number,title,state,createdAt,body,url \ | jq -r '.[] | "\(.number)|\(.title)|\(.state)|\(.createdAt)|\(.url)"' ` • Fetch PR bodies for context on what each PR does (use --json body). • Group PRs into two sections: • Features -- new capabilities, refactors, new providers, new APIs • Fixes -- bug fixes, dependency patches, config corrections, minor chores • Consolidate similar PRs under a single description when they share the same goal (e.g. two PRs making different parts of the SDK async-first). • Write the markdown file to docs/changelog-<username>.md using this format: `markdown
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster