Back to list
hohai99

release-notes-generator

by hohai99

0🍴 1📅 Jan 22, 2026

SKILL.md


name: release-notes-generator description: Generates accurate, user-facing release notes from specifications and approved changes. Use before every release. triggers: [pre-release, deployment-final-stage] outputs: [release-notes, change-log-entry]

Release Notes Generator

Purpose

Communicates the value and impact of changes to the end users and stakeholders. It ensures that every release is documented accurately and professionally.

When to use this skill

  • During the final stage of a release cycle
  • When preparing documentation for a production deployment
  • After a major feature or bug fix has been merged

Generation Steps

  1. Extract Approved Changes: Pull data from implementation_plan.md and approved spec updates.
  2. Categorize Changes:
    • New Features: User-facing additions.
    • Bug Fixes: Resolved issues.
    • Behavior Changes: Critical for existing users to know.
  3. Exclude Internal Noise: Ignore refactors, internal tooling updates, and minor formatting changes.
  4. Format for Audience: Use clear, non-technical language where possible.

Decision Tree

flowchart TD
    A[Gather Changes] --> B{User Facing?}
    B -->|No| C[Exclude from Release Notes]
    B -->|Yes| D{Bug Fix or Feature?}
    D -->|Bug| E[Add to 'Bug Fixes' Section]
    D -->|Feature| F[Add to 'New Features' Section]
    D -->|Behavioral| G[Add to 'Breaking Changes' Section]
    E --> H[Format & Publish]
    F --> H
    G --> H

Review Checklist

  1. Accuracy: Do the notes match the actual behavior of the code?
  2. Clarity: Are the descriptions understandable to someone not involved in the code?
  3. Completeness: Are any critical behavior changes missing?
  4. Tone: Is the language professional and helpful?

How to provide feedback

  • Be specific: "The note for 'Fast Login' doesn't mention that it requires a new client version."
  • Explain why: "Users on old clients will be confused when the feature doesn't work."
  • Suggest alternatives: "Add 'Requires Client v1.2.0+' to the feature description."

Release notes are a contract with users.

Score

Total Score

50/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon