Agent 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)

View SKILL.md on GitHub Repository
Stars 1
Forks 1

Install this agent skill to your Project

npx add-skill https://github.com/kwiggen/claude-code-plugin/tree/main/skills/release-reports

SKILL.md

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

bash
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

bash
# 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:

  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 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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

kwiggen/claude-code-plugin

gemini-reviewer

Dual code review: gets independent reviews from both Claude and Gemini API, then synthesizes agreements, unique findings, and a verdict. Use when users say "gemini review", "dual review", or want a second-perspective code review. Requires GEMINI_API_KEY environment variable to be set.

1 1
Explore
kwiggen/claude-code-plugin

pr-writer

This skill should be used when the user asks to "create a PR", "open a pull request", "write a PR description", "push and create PR", or needs to generate a best-in-class pull request description based on commits. Provides industry-standard PR description formatting following conventional commits, Microsoft Engineering Playbook, and HackerOne best practices.

1 1
Explore
kwiggen/claude-code-plugin

code-reviewer

Reviews code for logic flaws, edge cases, performance bottlenecks, security vulnerabilities, maintainability concerns, architecture best practices, and adherence to local patterns and CLAUDE.md guidelines. Use when users ask for code review or analysis, including reviewing uncommitted changes, the last local commit, unpushed code, or a specific GitHub pull request.

1 1
Explore
kwiggen/claude-code-plugin

antipattern-detector

Detects common failure patterns in proposals, architectures, plans, and decisions. Use when reviewing any plan to identify red flags before they become problems. Covers architecture, timeline, team, process, and technology anti-patterns. Works on any domain — not just code.

1 1
Explore
kwiggen/claude-code-plugin

github-insights

Provides team GitHub activity insights including merged PRs, contributor leaderboards, merge velocity, review participation, and PR size analysis. Use when users ask about team productivity, who merged PRs, code contribution stats, review patterns, or developer activity.

1 1
Explore
kwiggen/claude-code-plugin

teach-me

Pedagogical code walkthrough that teaches developers about their own code. Explains choices, tradeoffs, alternatives, and refactoring opportunities. Use when users say "teach me", "explain my changes", "walk me through", "what did I build", or want to understand their code at a deeper level. Works on uncommitted changes, last commit, unpushed commits, or a PR.

1 1
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results