AGENT SKILL

release-notes

Draft partner-facing release notes from the same commits as the changelog. Triggers on "draft release notes", "release notes for the next version", "/release-notes", "нотатки релізу", "release notes партнеру". Same input as curate-changelog, different audience and tone: a short, benefit-first narrative for a user or partner — "what's new for you" — not a categorized engineer's list. Keeps only changes a user actually notices; drops internal refactors and tooling. Prints the notes to the chat to seed a GitHub Release description or a partner announcement. Writes no file.

License 许可
MIT
最近更新
2026-11-12
Stars
★ 15
Forks
13

01 前言 Front Matter

name
release-notes
model
claude-haiku-4-5
effort
low
description
Draft partner-facing release notes from the same commits as the changelog. Triggers on "draft release notes", "release notes for the next version", "/release-notes", "нотатки релізу", "release notes партнеру". Same input as curate-changelog, different audience and tone: a short, benefit-first narrative for a user or partner — "what's new for you" — not a categorized engineer's list. Keeps only changes a user actually notices; drops internal refactors and tooling. Prints the notes to the chat to seed a GitHub Release description or a partner announcement. Writes no file.
allowed-tools
Bash(git log:*), Bash(git describe:*), Bash(git tag:*), Read(docs/**)
argument-hint
user-invocable
true
disable-model-invocation
true

02 资源文件 1

03 SKILL.md 正文

Skill: release-notes

Goal: write the human announcement of this release — a flowing, benefit-first narrative a non-engineer reads and immediately knows what changed for them.

Same commits as curate-changelog, different audience. The changelog is the engineer's categorized history; release notes are the user's story of one release. One input, two outputs — that contrast is the whole point.

Inputs

  • The commits since the last release (git log <tag>..HEAD) — the same raw input the changelog uses.
  • templates/release-notes.md — the narrative shape.

Protocol

  1. Find the baseline in docs/CHANGELOG.md and run git log <latest-tag>..HEAD --oneline --no-merges for the raw input.
  2. Keep only what a user notices — new capabilities and user-visible fixes. Drop internal refactors, tooling, and tests entirely.
  3. Write as flowing prose grouped by benefit, not by commit, following templates/release-notes.md:
    • Lead with what the reader can now do.
    • No internal jargon, no file names, no commit hashes.
    • Each line passes the test of a reader who never saw the code.
  4. Print the notes to the chat — do not write a file. They seed a GitHub Release description or a partner announcement.

Definition of Done

  • The notes read as a short benefit-first narrative, not a categorized list — that is what makes them different from the changelog on the very same input.
  • No file names, hashes, or internal jargon survive.
  • Printed to the chat; no file written, nothing committed.

Anti-patterns

  • Restating the changelog. If the output is a bulleted Added/Fixed list, you wrote a changelog, not release notes. Use prose, lead with the benefit.
  • Leaking internals. A partner does not care about refactor: or a file path. If it is not a user-visible change, it is not in the notes.
  • Writing a file. Print to the chat; the notes seed a Release description a human edits.

References & templates

  • templates/release-notes.md — partner-facing narrative scaffold.

04 同仓库更多 Skills

genkovich
genkovich/agentic-engineering-course-public

release

Run the whole local release pipeline in order, stopping at each human gate. Triggers on "run the release", "prepare a release", "/release", "зроби реліз", "підготуй реліз". Drives the four stages back to back — bump-version → curate-changelog → release-notes → check-docs-drift — pausing after each so the human reviews the diff before the next stage. Prepares everything in the working tree; never tags, commits, or pushes. The tag push (which fires CI) stays the human's action.

★ 15
genkovich
genkovich/agentic-engineering-course-public

curate-changelog

Curate the [Unreleased] section of docs/CHANGELOG.md from git history. Triggers on "curate the changelog", "update the changelog", "/curate-changelog", "онови changelog", "курування журналу". Reads git log since the last tag, FILTERS out what a reader never feels (test/ci/chore/merge), GROUPS commits about one feature into one bullet, and REWRITES technical subjects into plain language under the six Keep a Changelog categories (Added/Changed/Deprecated/ Removed/Fixed/Security). The result must have FEWER lines than the raw log — that is the proof of curation, not a dump. Leaves the edit in the working tree; never commits or pushes.

★ 15
genkovich
genkovich/agentic-engineering-course-public

codify-rule

Turn a repeated mistake into a durable, path-scoped rule in .claude/rules/. Triggers on "codify this rule", "make a rule so this doesn't happen again", "/codify-rule", "закодифікуй правило", "петля помилка-правило". Use only when the same mistake showed up TWICE (twice = a pattern, once = noise). Names the wrong shape and the right shape with one short example of each, scopes the rule to the paths that matter, and leaves the edit in the working tree so the next agent on this repo inherits the fix. Edits only .claude/rules/; never commits or pushes.

★ 15
genkovich
genkovich/agentic-engineering-course-public

check-docs-drift

Find and fix where docs/api.md fell behind the code. Triggers on "check for doc drift", "is the API doc up to date", "/check-docs-drift", "перевір дрейф документації", "docs drift". Runs the deterministic scripts/check-docs-drift.py (parses the public NoteBook methods with ast, compares to what docs/api.md documents — NO LLM finds the gap), reports the drift, and PROPOSES the doc edit that closes it. The gap is found by parsing; the agent writes the missing documentation in the doc's existing style. Edits only docs/; never commits or pushes.

★ 15
genkovich
genkovich/agentic-engineering-course-public

bump-version

Decide and apply the next semver for a release. Triggers on "bump the version", "what version is next", "/bump-version", "простав версію", "яка наступна версія". Reads the next number from the deterministic scripts/next-version.sh (NEVER guesses it), explains in plain language WHICH part moved and why (e.g. "MINOR, because a feat landed: filter notes by tag"), edits the version line in pyproject.toml, and proposes the matching `git tag vX.Y.Z`. The number is decided by a rule; the agent explains and applies — the human confirms the tag. Never pushes a tag itself.

★ 15
genkovich
genkovich/agentic-engineering-course-public

code-reviewer-subagent

Піднімає рев'юера у ЧИСТОМУ контексті, що бачить ЛИШЕ git diff + AC PR, і повертає дискретний вердикт ACCEPT/WARN/PARTIAL/REJECT з обґрунтуванням. Тригери — '/code-reviewer-subagent', 'дай рев'юера в чистому контексті', 'субагент має оцінити diff проти AC', 'review this diff with fresh eyes'. НЕ вбудований '/code-review'.

★ 15