OpenParable
Skip to content
← Back to skills

Sprint Review

Productivity
sprint-review

Sprint Review is an Agent Skill for productivity published in the rhesis-ai/rhesis repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/rhesis-ai/rhesis/blob/HEAD/.cursor/skills/sprint-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sprint-review, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  1. Detect the current user (unless explicitly provided):
gh api user --jq .login
  1. Collect PRs using GitHub CLI (default: last 14 days):
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)"'
  1. Fetch PR bodies for context on what each PR does (use --json body).

  2. Group PRs into two sections:

    • Features -- new capabilities, refactors, new providers, new APIs
    • Fixes -- bug fixes, dependency patches, config corrections, minor chores
  3. 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).

  4. Write the markdown file to docs/changelog-<username>.md using this format:

## PR Changelog -- <username> (<start date> -- <end date>)

### Features

**Short heading**

One-to-two sentence description.

- [#<number> -- <title>](<url>)
- [#<number> -- <title>](<url>) *(open/draft if not merged)*

### Fixes

**Short heading**

One sentence description.

- [#<number> -- <title>](<url>)

Formatting rules

  • Section headings: ### for Features / Fixes
  • Entry headings: bold text (not a markdown heading)
  • Descriptions: 1-2 sentences max, focus on what changed and why it matters
  • PR links: bulleted list with #<number> -- <title> as link text
  • Mark non-merged PRs with (open) or (draft)
  • No emojis