Skill

release-reports

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)

From kw-plugin

Install

Run in your terminal

npx claudepluginhub kwiggen/claude-code-plugin --plugin kw-plugin

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

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

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Stars1

Forks1

Last CommitFeb 8, 2026

Actions

View Source View Plugin View on GitHub View README

Release Reports Skill

Generate reports for weekly release cycles.

Available Actions

Action	Description
`preview`	Release preview - what's shipping, risk flags
`retro`	Release retro - what happened, hotfixes, trends

Usage

node {baseDir}/dist/releases/cli.js --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
node {baseDir}/dist/releases/cli.js --action preview

# Tuesday morning after prod is stable
node {baseDir}/dist/releases/cli.js --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:

Generate polished, user-facing release notes
Rewrite each PR title as a clear one-line summary focusing on user impact
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
Do NOT include PR links (this is for external sharing)
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 Type	Base	Head	Description
Feature	develop	feature/*	Normal development
Release train	staging	develop	Weekly release
Hotfix	staging	fix/*	Direct fix during QA
Promotion	release	staging	Push to production
Backmerge	develop	staging	Sync hotfix back

Output

Reports include emoji indicators for quick scanning:

✅ Clean / Good
⚠️ Needs attention
❌ Action required