RE

release-notes

Ensures consistent, high-quality narratives for GitHub release notes that go beyond auto-generated changelogs.

Install

mkdir -p .claude/skills/release-notes-certamesh && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13214" && unzip -o skill.zip -d .claude/skills/release-notes-certamesh && rm skill.zip

Installs to .claude/skills/release-notes-certamesh

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when drafting GitHub release notes for piinuts/gaze, gaze-lens, or gaze-laravel — including new releases, RC pre-releases, and re-writes of auto-generated notes. Enforces the curated-narrative voice destilled from v0.4.5 (TL;DR → Highlights → Known limitations → Adopter notes → Download → CHANGELOG link), past-tense PR-anchored prose, and a North-Star tie. Counter-pattern: auto-generated Keep-a-Changelog dumps with Added/Changed bullets are NOT acceptable as release-notes voice (they are fine in CHANGELOG.md only). Trigger phrases: "draft release notes", "release notes for vX.Y.Z", "rewrite the release body", "publish v…".
634 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Draft GitHub release notes for `piinuts/*` repositories
  • →Rewrite auto-generated release bodies into a curated narrative
  • →Apply a specific structure and voice to release notes
  • →Anchor release notes to the project's North-Star principle
  • →Include known limitations with documentation links and todo numbers
  • →Provide adopter notes with concrete migration recipes

How it works

The skill applies a predefined structure and voice to release notes, ensuring they are a curated narrative rather than a raw changelog dump, and includes specific sections like TL;DR, Highlights, and Adopter notes.

Inputs & outputs

You give it
A request to draft or rewrite GitHub release notes for a `piinuts/*` repository
You get back
Structured and curated GitHub release notes following a specific voice and format

When to use release-notes

  • →Drafting release notes
  • →Rewriting auto-generated release bodies
  • →Reviewing release note quality

About this skill

Release notes

Use for GitHub Releases. Keep CHANGELOG.md in Keep a Changelog format. The v0.4.5 release is the voice reference; auto-generated Added/Changed dumps need rewriting.

Required structure

Keep this order. Omit Known limitations only when none ship.

SectionContent
Opening1–3 sentences: release id, bundle context, and main changes.
## TL;DROne prose paragraph covering major changes, feature gates, and behavior shifts.
## HighlightsOne paragraph per major item, usually at most four: [Feature] landed in PR #N. [What] using [how]. [Adopter implication].
## Known limitationsName each accepted gap, link its docs/ page, and state the planned fix release or public GitHub follow-up. Never include private tracker ids.
## Adopter notesDefaults, fail-closed paths, repository/distribution moves, and exact migration commands. State platform/dependency versions precisely, such as glibc 2.39+.
## DownloadBinary and SHA256 sidecar links per platform: Apple Silicon macOS, Linux x86_64, then others.
## Full CHANGELOGOne link to the release anchor, for example CHANGELOG.md#045.

Tie the opening or TL;DR to Gaze’s contract: fail closed, preserve reversibility, keep PII out of agent-visible surfaces.

Voice rules

Use past-tense, third-person prose with artifacts as subjects. Put PR anchors inline. Preserve exact crate, flag, feature, and error names. Use prose for Highlights and bullets for downloads. No first person, emojis, marketing claims, backslash-escaped backticks, or Added/Changed sections.

Example: “DE and US national phone recognizers landed in PR #58. They use phonenumber for E.164 region-aware validation through core-extended.”

Worked skeleton

[Release id, bundle context, main changes, and Gaze contract.]

## TL;DR

[One paragraph: major changes, gates, behavior shifts.]

## Highlights

[Feature] landed in PR #N. [What] using [how]. [Adopter implication].

## Known limitations

[Gap, docs link, planned fix or public follow-up. Omit only if none.]

## Adopter notes

[Exact migration commands, defaults, distribution and platform constraints.]

## Download

- Apple Silicon macOS: [URL for gaze-aarch64-apple-darwin]
- SHA256: [URL for gaze-aarch64-apple-darwin.sha256]
- Linux x86_64: [URL for gaze-x86_64-unknown-linux-gnu]
- SHA256: [URL for gaze-x86_64-unknown-linux-gnu.sha256]

## Full CHANGELOG

[Absolute repository URL for CHANGELOG.md#XYZ]

Pre-publish checklist

Check section order, opening length, contract tie, inline PR anchors, exact names/constraints, documented gaps, migration steps, binary/checksum pairs, and the correct changelog anchor. Check voice rules above.

Failure mode: starting from auto-generated notes

Copy generated notes to a scratch buffer. Group major changes into Highlights prose; leave minor changes in CHANGELOG. Fill the skeleton, run the checklist, and replace the release body.

Out of scope

Commits follow AGENTS.md. PRs follow the PR template. CHANGELOG retains its own format; website marketing has its own voice.

When not to use it

  • →When generating `CHANGELOG.md` files
  • →When writing internal commit messages
  • →When drafting pull-request descriptions

Limitations

  • →It does not replace `CHANGELOG.md`
  • →It does not govern internal commit messages
  • →It does not govern pull-request descriptions

How it compares

This skill enforces a specific, curated narrative voice and structure for GitHub release notes, explicitly avoiding auto-generated changelog dumps and integrating project-specific principles, unlike generic release note generation.

Compared to similar skills

release-notes side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
release-notes (this skill)04moReviewIntermediate
docs-write229moNo flagsBeginner
content-research-writer151yNo flagsBeginner
doc-coauthoring1611moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

docs-write

metabase

Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).

22139

content-research-writer

ComposioHQ

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

15111

doc-coauthoring

anthropics

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

1686

research-grants

davila7

Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.

694

teams-channel-post-writer

daymade

Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.

591

write-docs

tldraw

Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.

665

Search skills

Search the agent skills registry