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".
Install
/plugin marketplace add backnotprop/plannotatorThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add backnotprop/plannotator --skill release-plannotatorgit clone --depth 1 https://github.com/backnotprop/plannotator.git /tmp/plannotator
mkdir -p ~/.claude/skills
cp -r /tmp/plannotator/.agents/skills/release ~/.claude/skills/release-plannotatorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 creators** — who started relevant GitHub Discussions - **Feature requestors** — check the linked "closes #N" issues and their authors Use the GitHub API via `gh`:
Details
- Skill name
release-plannotator- Repository
- backnotprop/plannotator
- Path
.agents/skills/release/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
FAQ
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 the Release Plannotator skill?
Claude Code plugin: /plugin marketplace add backnotprop/plannotator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Release Plannotator popular?
It lives in backnotprop/plannotator, which has 13,329 GitHub stars and 1,343 forks, and is included in 2 curated skill lists.
Related skills
Plannotator
13kbacknotprop/plannotator
Reference for using Plannotator (its `plannotator` tool when you have one, otherwise the CLI): plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, exporting or sharing Guided Reviews, and the Plannotator Inbox (messages and questions the person answers later, without blocking you). Invoke when asked to use Plannotator for anything not covered by a more specific plannotator-* skill, and before you leave the person a decision, a question or finished work in the Plannotator Inbox (if another ag
Plannotator Annotate
13kbacknotprop/plannotator
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
Plannotator Annotate
13kbacknotprop/plannotator
Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.
Update Deps
13kbacknotprop/plannotator
Audit and update npm/Bun dependencies with supply chain integrity checks — verifies maintainers, publish age, tarball diffs, and provenance before bumping. Defers risky packages to ~/.supply-chain/notes/.
Screenpipe Workflow Maintenance
22kscreenpipe/screenpipe
Investigate and review evidence-backed workflows with Screenpipe tools and shared drafts.
P7
20ktanweai/pua
P7 Senior Engineer mode — solution-driven execution under P8 supervision. Use when user says 'P7模式', '方案驱动', or when spawned as sub-task executor by P8. Produces: implementation plan + code + 3-question self-review, delivered via [P7-COMPLETION].
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.