メニュー
"Use when preparing release notes, classifying changes, or drafting upgrade/breaking-change communications. Triggers on "release notes", "changelog", "version", "ship", "customer-facing communication"."
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | Release Notes Generation |
| description | "Use when preparing release notes, classifying changes, or drafting upgrade/breaking-change communications. Triggers on "release notes", "changelog", "version", "ship", "customer-facing communication"." |
| Audience | Tone | Detail |
|---|---|---|
| End users | Plain language, benefits-first | "What's new for me?" |
| Integrators / API consumers | Precise, breaking-change callout | Migration code |
| Ops / SRE | Operational impact, rollback plan | Config changes |
| Internal teams | Technical, links to PRs | Everything |
Write one note per audience if the release is significant. A single note for everyone is a compromise nobody loves.
# Release v2.4.0 - 2026-04-28
## BREAKING CHANGES
- API endpoint `/users/{id}/roles` now returns paginated results.
**Migration**:
```diff
- const roles = await api.getUserRoles(id);
+ const { data: roles } = await api.getUserRoles(id, { page: 1 });
V24__role_pagination.sql.Thanks: @alex, @sam, @jordan.
## Anti-patterns
- "Various improvements and bug fixes" (zero signal).
- Breaking change hidden in "Changed" section.
- Copy-paste of PR titles (jargon-heavy, unclear).
- No rollback plan.
- Missing version number.
## Quality gate
Reject release if any breaking change lacks a migration snippet or rollback instructions.
"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."
"Use when mapping business capabilities, identifying overlap or gaps across the enterprise, or aligning IT investments to business outcomes. Triggers on "capability map", "business capability", "domain map", "enterprise architecture"."
"Use when drafting Architecture Decision Records, evaluating alternatives, or documenting technical trade-offs. Triggers on "ADR", "architecture decision", "trade-off", "pick between", "why did we choose"."
"Use when a new engineer joins the team, when onboarding to an unfamiliar codebase, or when auditing whether the team has shared understanding. Triggers on "onboard", "context", "knowledge gap", "bus factor", "team understanding"."
Use when refactoring legacy code, extracting a service, or making behavior-preserving changes. Triggers on 'refactor', 'legacy code', 'strangler fig', 'characterization test', 'mikado method'.
Use when practicing test-driven development, writing a failing test first, or coaching red-green-refactor. Triggers on 'TDD', 'red-green-refactor', 'test first', 'failing test', 'write a test'.