release-note-draft
/release-note-draft
Draft structured release notes from git history. Use when the user wants to write release notes, a changelog entry, a sprint summary, or wants to know what changed since a tag, branch, or previous release — even without the phrase "release notes". Not for publishing, tagging, or explaining a single commit in isolation; not for general writing that mentions versions.
- Author
- rolling-codes ↗
- Repository
- better-skill-creator ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Draft structured release notes from git history. Use when the user wants to write release notes, a changelog entry, a sprint summary, or wants to know what changed since a tag, branch, or previous release — even without the phrase "release notes". Not for publishing, tagging, or explaining a single commit in isolation; not for general writing that mentions versions.
Triggers from the description
Original author description
Draft structured release notes from git history. Use when the user wants to write release notes, a changelog entry, a sprint summary, or wants to know what changed since a tag, branch, or previous release — even without the phrase "release notes". Not for publishing, tagging, or explaining a single commit in isolation; not for general writing that mentions versions.
How it works
- Capability
- When to use
- When NOT to use
- Workflow
- Output format
- Iron Law
- Reference files
SKILL.md preview
--- name: release-note-draft description: >- Draft structured release notes from git history. Use when the user wants to write release notes, a changelog entry, a sprint summary, or wants to know what changed since a tag, branch, or previous release — even without the phrase "release notes". Not for publishing, tagging, or explaining a single commit in isolation; not for general writing that mentions versions. allowed-tools: - Read - Bash(git describe *) - Bash(git log *) - Bash(git diff *) - Bash(git show *) metadata: schemaVersion: "1" --- # Release Note Draft Turn git history into a structured, human-readable release notes draft. ## Capability Run `git log` and `git diff` to gather commits between two refs (or from the last tag to HEAD), group changes into standard categories, and return a Markdown draft for the user to review. The draft is never published or pushed automatically. ## When to use - User names a version, tag, or range: "write release notes for v2.1", "what changed since v1.0" - User asks for a work summary: "summarize what changed since last release", "draft a changelog entry for this sprint", "what's new since the last tag" - User wants release notes for a PR: "summarize this PR for the changelog" - User asks about changes without release-note language: "what went in this week", "what changed since the last tag" ## When NOT to use - User wants to *publish*, *tag*, or *push* a release — ask for explicit confirmation before any write action; do not proceed automatically - User wants to understand what a *single specific commit* does, not summarize it - User wants a general writing task (email, blog post, document) that mentions a version ## Workflow 1. **Identify the range.** If the user supplied a tag, branch, or SHA range, use it directly. If they said "last N commits", use `HEAD~N..HEAD`. If no range is given, run `git describe --tags --abbrev=0` to find the last tag and default to `<tag>..HEAD`. If there are no tags and no range, use the full log. If `git log` returns nothing, tell the user there is no history yet and stop — do not invent changes. 2. **Collect commits.** Run `git log --oneline <range>`. If the range covers more than 50 commits, report the count and ask whether to summarize or continue. 3. **Inspect significant commits.** For non-trivial subjects, run `git show <sha>` to read the full diff and confirm what actually changed. Do not rely on the subject line alone. 4. **Group changes** under: **Added**, **Changed**, **Fixed**, **Removed**, **Security**. Omit empty categories. 5. **Write bullets** in user-facing language — what changed and why it matters, not the raw commit subject. 6. **Return a Markdown draft.** Label it clearly as a draft. List ambiguous or skipped commits at the bottom. ## Output format ```markdown ## v2.1.0 — 2026-09-08 ### Added - Users can now filter results by date range. ### Fixed - CSV exports no longer contain duplicate rows when pagination is active. --- *Draft — review before publishing. Skipped: abc1234 (merge commit).* ``` ## Iron Law Never invent a change that is not traceable to a commit in the supplied range. If the history is ambiguous, omit the claim or ask — misleading release notes erode trust faster than sparse ones. | Rationalization | Correct behavior | |---|---| | "The commit subject says 'fix auth'; I'll add details about what was fixed." | Write only what the commit and its diff confirm. If the diff is unclear, write "Authentication fix (details TBD)" and flag it. | ## Reference files - `tests/expected_behavior.yaml` — two authored behavior cases (happy path and graceful failure); read when uncertain about output format or handling of missing history.
Files in this package (4)
- SKILL.md 4 KB
- tests/expected_behavior.yaml 1 KB
- tests/should_not_trigger.yaml 1 KB
- tests/should_trigger.yaml 1 KB
Versions
The database has no other skills named release-note-draft.
Database snapshot: 13.11.2026 · package version 5034fc2211ef (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100changelog
Write release notes or a CHANGELOG.md entry from git history. Use when the user says "write the changelog", "release notes for v2.3", "what changed since the last release/tag", or is preparing a release or version bump. - 100draft-release
Draft a GitHub release (as a draft, not published) for an upcoming obot minor release by analyzing git history since the previous release. Use when the user asks to draft a release, prepare release notes, or write release notes for an upcoming vX.Y.0 release. Creates a DRAFT… - 100release-notes
Write release notes or a changelog entry from git history. Use when the user asks for release notes, a changelog, "what changed since the last release", or a summary of commits between two tags or branches. - 90release-notes
Write release notes or a CHANGELOG entry from the commits and merged PRs since the last release. Use when asked for "release notes", "update the changelog", "what changed since v1.2", or before tagging a release. - 90changelog-updates
Use when a release or a since-tag window needs user-facing release notes drafted. Not for publishing the release. - 90release-notes
Builds release notes from merged pull requests and git history. Use when the user asks for release notes, a changelog, or a summary of changes between versions.