release-plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".
Profile →npx skills add backnotprop/plannotator --skill release --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Plannotator Release The process has four phases. Phase 1 (release notes) is where most of the work happens — present the draft for review before proceeding to later phases. ## Phase 1: Draft Release Notes This is the most important phase. The release notes are the public face of each version and the primary way the community sees their contributions recognized. ### Step 1: Determine scope 1. Find the latest release tag: `git tag --sort=-v:refname | head -1` 2. Determine the new version number. Ask the user if unclear (patch, minor, or major). 3. Gather all changes since the last tag: - `git log --oneline <last-tag>..HEAD` for commit history - `git log --merges --oneline <last-tag>..HEAD` for merged PRs 4. For each PR, use `gh pr view <number> --json title,author,body,closedIssues,labels` to get details. ### Step 2: Research contributors This is critical. Every person who participated in the release gets credit — not just PR authors. For each PR and linked issue, collect: - **PR authors** — the person who wrote the code - **Issue reporters** — who filed the bug or feature request - **Issue commenters** — who participated in the discussion with useful context - **Discussion creator
- Phase 1: Draft Release Notes
- Step 1: Determine scope
- Step 2: Research contributors
- Step 3: Write the release notes
- Step 4: Present for review
- Phase 2: Version Bump
- Phase 3: Build
- Pi Parity Gate
- Phase 4: Commit, Tag, and Release
- Checklist
Get issue details including author gh issue view <number> --json author,title,body Get issue comments to find participants gh api repos/backnotprop/plannotator/issues/<number>/comments --jq '.[].user.login' Get PR review comments gh api repos/backnotprop/plannotator/pulls/<number>/comments --jq '.[].user.login' bun run build:review # 1. Code review editor (standalone Vite build) bun run build:hook # 2. Plan review + hook server (copies review's built HTML into hook dist) bun run build:opencode # 3. OpenCode plugin (copies built HTML from hook + review) bun run build:pi # 4. Pi extension (chains review → hook → pi internally, safe to run after 1-2)
What does the release-plannotator skill do?
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".
How do I install it?
Run `npx skills add backnotprop/plannotator --skill release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From backnotprop/plannotator, a repository with 7,510 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.