OpenParable
Skip to content
← Back to skills

Release Reports

Productivity
release-reports

Release Reports is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generates weekly release cycle reports for the team. - preview: What's shipping (run Sunday after release train) - retro: What happened (run Tuesday after prod stabilizes)

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/majiayu000/claude-skill-registry/blob/HEAD/skills/data/release-reports/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/release-reports, 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.

Release Reports Skill

Generate reports for weekly release cycles.

Available Actions

ActionDescription
previewRelease preview - what's shipping, risk flags
retroRelease retro - what happened, hotfixes, trends

Usage

python {baseDir}/skills/release-reports/scripts/release_reports.py --action <ACTION> [OPTIONS]

Options

  • --action (required): preview or retro
  • --days N: Days to look back for release trains (default: 30)

Examples

# Sunday evening after release train is merged
python {baseDir}/skills/release-reports/scripts/release_reports.py --action preview

# Tuesday morning after prod is stable
python {baseDir}/skills/release-reports/scripts/release_reports.py --action retro

Report Details

Preview Report

Run after the develop → staging PR is merged (Sunday).

Shows:

  • Release train PR details
  • All feature PRs in this release
  • Risk flags: large PRs (500+ lines), quick approvals
  • Hotfixes from previous cycle that need backmerge
  • Monday QA focus areas
  • Release notes data for AI generation

Release Notes Generation

The preview report outputs structured PR data in <release-notes-data> tags. When you see this data:

  1. Generate polished, user-facing release notes
  2. Rewrite each PR title as a clear one-line summary focusing on user impact
  3. Group items into these categories (skip empty ones):
    • What's New - New features and capabilities
    • Bug Fixes - Problems that were resolved
    • Improvements - Enhancements to existing functionality
  4. Do NOT include PR links (this is for external sharing)
  5. Use professional, concise language

Example output:

## Release Notes

### What's New
- Users can now export reports in PDF format
- Added dark mode support across all pages

### Bug Fixes
- Fixed crash when loading large datasets
- Resolved timezone display issues in reports

### Improvements
- Improved search performance by 40%
- Streamlined onboarding flow

Retro Report

Run after production is stable (Tuesday).

Shows:

  • Release timeline (staging date, prod date)
  • Outcome (clean release or hotfixes required)
  • What shipped (PRs, contributors, lines)
  • Hotfixes during QA with backmerge status
  • Trend of last 4 releases

Branch Model

PR TypeBaseHeadDescription
Featuredevelopfeature/*Normal development
Release trainstagingdevelopWeekly release
Hotfixstagingfix/*Direct fix during QA
PromotionreleasestagingPush to production
BackmergedevelopstagingSync hotfix back

Output

Reports include emoji indicators for quick scanning:

  • ✅ Clean / Good
  • ⚠️ Needs attention
  • ❌ Action required