write-release-note

Included with Lifetime

$97 forever

Release note content structure and guidelines for GitHub Releases.

Writing & Docs

What this skill does


# Write Release Note

Generate concise release notes from a branch story for GitHub Releases.

## Content Structure

```markdown
# <Story Title>

## Summary

<2-3 sentence overview extracted from story section 1>

## Key Changes

- <Highlight 1 from story>
- <Highlight 2 from story>
- <Highlight 3 from story>

## Changes

### Added
- <Entry from story Section 4 where ticket category is "Added">

### Changed
- <Entry from story Section 4 where ticket category is "Changed">

### Removed
- <Entry from story Section 4 where ticket category is "Removed">

## Metrics

- **Tickets Completed**: <tickets_completed from frontmatter>
- **Commits**: <commits from frontmatter>
- **Duration**: <duration_days from frontmatter> days (<duration_hours from frontmatter> hours)
- **Velocity**: <velocity from frontmatter> commits/<velocity_unit from frontmatter>

## Links

- [Pull Request](PR-URL)
- [Branch Story](.workaholic/stories/<branch-name>.md)
```

## Guidelines

1. **Summary**: Extract the essence of section 1 (Overview) from the story. Keep it under 50 words.

2. **Story Title (H1)**: Extract the first highlight from section 1 (Overview). Use the same derivation logic as PR title: first highlight text, appending "etc" if multiple highlights exist.

3. **Key Changes**: Use the highlights from section 1. If fewer than 3 highlights, summarize the most impactful changes from section 4 (Changes).

4. **Changes**: Group entries from story Section 4 by their ticket `category` frontmatter (Added, Changed, Removed). Each entry should be a concise one-line summary of the ticket change. Omit empty subsections.

5. **Metrics**: Extract from story frontmatter:
   - `tickets_completed` field
   - `commits` field
   - `duration_hours` field (round to 1 decimal place)
   - `duration_days` field (use when available)
   - Format duration as: "N days (N hours)" when both fields exist, "N hours" when only hours exist
   - `velocity` field (round to 1 decimal place)
   - `velocity_unit` field
   - Format velocity as: "N commits/<unit>"
   - Omit velocity line when fields are absent

6. **Links**: PR URL is provided as input to the release-note subagent. Always include it.

## Output Location

Write release notes to `.workaholic/release-notes/<branch-name>.md`

## Writing Style

- Use active voice
- Focus on user-facing impact
- Keep total length under 200 words
- No emojis
- No technical jargon unless necessary

Files: 1

Size: 2.5 KB

Complexity: 10/100

Category: Writing & Docs

Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/write-release-note

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts