release-notes
Skill3 starsChanged 14 days agoMITView on GitHub
Write and publish Dispatch release notes for a shipped milestone, in the house narrative style, with a mandatory screen-recorded demo GIF attached to the GitHub release. Also writes the changelog entry that the Dispatch site shows. Trigger when the user says "release notes", "write the release", "publish the release", "do the release", or at the publish step of a milestone ship ritual.
- Commits and pushes
185 other projects use a version of this.
Adopted by
Most recently taken up by
- xmartlabs/agent-skillstheir own version, first seen Nov 16, 2026
- yearzen1/LocalSkillManagertheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- neomjs/neo-agent-skillstheir own version, first seen Nov 15, 2026
- homarr-labs/homarrtheir own version, first seen Nov 15, 2026
- microsoft/frontier-ghcp-ttt-rvastheir own version, first seen Nov 15, 2026
Used with
Projects with it also use brainstorm-experiments-existing, brainstorm-ideas-new and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 6 projects that use this
skytiger6724Skillbrainstorm-ideas-new
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Also in 6 projects that use this
45ckSkillpestle-analysis
Also in 6 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 6 projects that use this
About-IntelligenceSkillproduct-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 6 projects that use this
- +7 more from skytiger6724
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- tw93/Mole★ 75ksame name
- makeplane/plane★ 62ksame name
- tabler/tabler★ 42ksame name
- pnpm/pnpm★ 37ksame name
- quasarframework/quasar★ 27ksame name
- dotnet/core★ 22ksame name
- zauberzeug/nicegui★ 16ksame name
- adobe/react-spectrum★ 16ksame name
- espanso/espanso★ 15ksame name
- formbricks/formbricks★ 13ksame name
175 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-shadcn-componentSkill
- scaffold-backend-sliceSkill
- scaffold-moduleSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 8 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Write the release notes for one Dispatch version.
- Distinctive: line 18
Read these before you draft.
- Very specific: line 30
Use ## sections. Each section tells one part of the story: the main feature, what changed underneath, upgrade notes, known limits.
- Distinctive: line 35
Never use an em dash or a double hyphen.
- Very specific: line 43
Start the release body with this hidden title line, then one blank line: [//]: # (Release title: vX.Y.Z - <short name>.
- Distinctive: line 45
After the blank line, write one summary paragraph of exactly one sentence.
- Very specific: line 48
After the summary, write the narrative opener from the style contract, then the other ## sections.
- Very specific: line 51
After the publish, verify: gh run list --workflow "Changelog sync" --limit 1.
- Very specific: line 52
If the repository secret SITE_DEPLOY_TOKEN is empty, the job prints one line and skips.
- Distinctive: line 78
Every release carries one screen-recorded flow of the headline feature, shown three ways: an inline player with narration, a short silent …
- Distinctive: line 90
Read the sources. Pick the one headline feature.
- Distinctive: line 99
Do not publish a release body the user did not approve.
- Distinctive: line 100
Do not skip the recording.
- Very specific: line 101
Do not run git push. Only /ship pushes.
- Distinctive: line 102
Do not invent facts absent from the source documents.
“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release Notes
This file in the repository is the source of truth for Dispatch release notes. A user-level copy can exist at ~/.claude/skills/release-notes. That copy is older. When the two differ, follow this file.
Write the release notes for one Dispatch version. Publish them as a GitHub release. Attach a screen-recorded demo GIF. Every release must have a recording. A text-only release is incomplete.
Sources
Read these before you draft. Do not draft from memory.
.planning/MILESTONES.md, the entry for this version..planning/milestones/<version>-MILESTONE-AUDIT.md, for requirement coverage and named residuals..planning/milestones/<version>-ROADMAP.md, for the phase list and the "What shipped" summary.- Two or three previous release bodies for style:
gh release view v3.0.0 --json body -q .body.
Style contract
The house style is narrative prose, not a bullet changelog. Follow these rules:
- Open with the user's problem, told as a short story. Do not open with a feature list. The narrative opener comes after the hidden title line and the summary sentence (see Changelog entry). Example openers: "A ticket used to mean a session." (v3.0.0).
- Use
##sections. Each section tells one part of the story: the main feature, what changed underneath, upgrade notes, known limits. - State limits and residuals plainly. Name what does not work. Do not round a partial result up to "done".
- Include a
## See itsection with the demo GIF and a link to the higher-quality MP4 (see Recording below). - End with two lines: the full-changelog compare link (
https://github.com/theyashgupta/dispatch/compare/<prev>...<this>), then the requirements footer: "Requires Node ≥ 22.22, tmux, ttyd, git, and the Claude Code CLI. Setup is in the README." - Apply the
asd-ste100skill in STE-flavored mode to the draft. Invoke the skill. Do not approximate it. - Never use an em dash or a double hyphen. Use a single hyphen, a comma, or a new sentence.
- Title format:
<tag> - <short name>. Example:v3.2.0 - Vault: environment keys inside Dispatch.
Changelog entry
The Dispatch site shows every published release in its changelog feed. Every release goes to the changelog.
- The feed reads the release body.
- Start the release body with this hidden title line, then one blank line:
[//]: # (Release title: vX.Y.Z - <short name>. This line is hidden when the release renders.) - The title in the hidden line is the same as the release title.
- After the blank line, write one summary paragraph of exactly one sentence.
- The site shows this sentence in its feed. It states the user benefit of the release.
- The summary has no link, no image and no markdown heading.
- After the summary, write the narrative opener from the style contract, then the other
##sections. - The title format stays
vX.Y.Z - <short name>. Use a single hyphen with spaces. Do not put a parenthesis in the short name, because it breaks the hidden title line. - Publishing the release (draft to published) starts the
Changelog syncworkflow (.github/workflows/changelog-sync.yml). The workflow sends therelease-publishedevent totheyashgupta/dispatch-site. The site then redeploys. - After the publish, verify:
gh run list --workflow "Changelog sync" --limit 1. - If the repository secret
SITE_DEPLOY_TOKENis empty, the job prints one line and skips. Tell the user to add the secret.
Body skeleton:
[//]: # (Release title: v3.2.0 - Vault: environment keys inside Dispatch. This line is hidden when the release renders.)
Keep environment keys in Dispatch, so no session needs a pasted secret.
A session used to start with a hunt for the right key.
## Vault
...
## See it
...
Full changelog: https://github.com/theyashgupta/dispatch/compare/v3.1.0...v3.2.0
Requires Node ≥ 22.22, tmux, ttyd, git, and the Claude Code CLI. Setup is in the README.Recording (mandatory)
Every release carries one screen-recorded flow of the headline feature, shown three ways: an inline player with narration, a short silent GIF preview, and the MP4 as a download.
- Invoke the
record-flowskill to record the flow in a real browser against a running app. For Dispatch, start the built tree with/Users/yash/dispatch-workspaces/release-sandbox.sh start <worktree> <port above 48800> <label>(stub claude, fresh HOME, no sources). Show the caption list to the user and get approval before recording. - Render twice from the same
raw.mp4: the narrated take withrender.py <job>/video <slug>and a silent take for the GIF withrender.py <job>/video <slug>-gif --silent --pace fast --no-zoom. - Name the files
dispatch-<tag>-<slug>.mp4(the narrated take) anddispatch-<tag>-<slug>.gif. Make the GIF with a two-pass palette and a 2 second end hold so the loop restarts cleanly:ffmpeg -i <silent>.mp4 -vf "tpad=stop_mode=clone:stop_duration=2,fps=12,scale=1280:-1:flags=lanczos,split[a][b];[a]palettegen=stats_mode=diff[p];[b][p]paletteuse=dither=bayer:bayer_scale=5:diff_mode=rectangle" -loop 0 <out>.gif. - Upload both as release assets:
gh release upload <tag> <files>(works on a draft release too). - Inline player: GitHub renders a video player only for files dropped into its own markdown editor (
github.com/user-attachments/assets/<id>), never for release assets. From the repository root, runnode .claude/skills/release-notes/gh-attach.js upload "https://github.com/theyashgupta/dispatch/releases/edit/<tag or untagged id>" <mp4> --save. The script loads playwright from~/.cache/record-flow/node_modulesby absolute path, so the working directory does not matter. It drives a signed-in Chromium profile (~/.cache/record-flow/github-profile) headlessly and printsATTACHMENT_URL=<url>. If it reports "not signed in", runnode .claude/skills/release-notes/gh-attach.js loginonce: a window opens, the user signs in, the script closes it. - The
## See itsection is, in order: the attachment URL on its own line (the inline player), the GIF as an image with a descriptive alt text, then "Higher-quality video with narration:" linking the MP4 asset by its download URLhttps://github.com/theyashgupta/dispatch/releases/download/<tag>/<file>.
Process
- One version per PR. Main takes squash merges, so a PR that bundles two milestones collapses them into one commit: the tags share a commit, the between-tags changelog compare is empty, and npm can never publish the earlier version. If a branch spans milestones, ship the earlier version's PR first, merge and tag it, then open the next. Write every release PR's description with the standard template from the
pr-description-standardmemory (Summary, Type of Change, What Changed, Why, Risk & Edge Cases, Testing, Reviewer Focus). Never write an ad hoc PR body. - Read the sources. Pick the one headline feature. The headline is what the recording shows.
- Draft the notes to a scratch file. Apply the style contract and the changelog entry rules.
- Show the full draft to the user. Wait for approval. Do not publish an unapproved draft.
- Create the release as a DRAFT first:
gh release create <tag> --draft --target <full-sha> --title "<title>" --notes-file <draft>. A draft creates no tag, so the body can be completed before anything is public. The target is the squash commit on main, or the bump branch tip when the release is cut behind main (see the release-split memory). Confirm with the user before this step anyway, because the publish that follows creates the tag. - Record the flow, render, upload the assets, run
gh-attach.js uploadfor the inline player, fill the asset URLs into the notes, then publish:gh release edit <tag> --notes-file <final> --draft=false --latest. Verify withgh release view <tag>andgit fetch --tags. Then verify the changelog sync (see Changelog entry). - npm ritual: the version bump lands via the release PR. Publishing is AUTOMATIC:
.github/workflows/publish.ymlruns on a pushedv*tag, and publishing the release creates that tag. After the publish, verify withnpm view @theyashgupta/dispatch version(expect the new version within ~2 minutes) and checkgh run list --workflow Publish --limit 1. ONLY if the workflow is missing or failed, publish manually with the vault token, never an interactive login:NPM_CONFIG_USERCONFIG=$HOME/.claude/env-vault/publish.npmrc ~/.claude/scripts/with-env.sh npm publish. The token isNPM_TOKENin the env-vault (see the npm-publish-token memory). Only if the token is missing or rejected, ask the user to run! npm loginand flag the token for regeneration. The version-bump commit must reach main signed. If the YubiKey is not connected, commit locally unsigned and flag the commit for re-sign at the next/ship.
Boundaries
- Do not publish a release body the user did not approve.
- Do not skip the recording. If recording is impossible now, publish only with the user's explicit consent, and record the gap as a follow-up task.
- Do not run
git push. Only/shippushes. - Do not invent facts absent from the source documents.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

