release-plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency…
Connecting the steps of a workflow
What it does
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.
Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the 4 files in the skill’s folder on GitHub; none is a script or program.
Mentions 4 outside web addresses
The instructions point your AI at these sites or APIs. Anything it sends there leaves your computer.
How we know
Web addresses in the SKILL.md, excluding GitHub and documentation sites: cyclonedx.org, docs.plannotator.ai, slsa.dev, x.com.
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
Downloads a script and runs it in one step, unread
Code run this way does whatever the other server sends at that moment — what you can read today is not necessarily what runs.
How we know
references/release-notes-v0.12.0.md line 107 (and 1 more in that file): “curl -fsSL https://plannotator.ai/install.sh | bash”. Read 2026-10-05, commit 152cfd9.
references/release-notes-v0.12.0.md, line 107 ↗Downloads a script and runs it in one step, unread
Code run this way does whatever the other server sends at that moment — what you can read today is not necessarily what runs.
How we know
references/release-notes-v0.13.0.md line 92 (and 1 more in that file): “curl -fsSL https://plannotator.ai/install.sh | bash”. Read 2026-10-05, commit 152cfd9.
references/release-notes-v0.13.0.md, line 92 ↗Downloads a script and runs it in one step, unread
Code run this way does whatever the other server sends at that moment — what you can read today is not necessarily what runs.
How we know
references/release-notes-v0.13.1.md line 58 (and 1 more in that file): “curl -fsSL https://plannotator.ai/install.sh | bash”. Read 2026-10-05, commit 152cfd9.
references/release-notes-v0.13.1.md, line 58 ↗3 smaller things worth knowing
Contains commands that delete or overwrite. Usually legitimate — listed so nothing is hidden.
How we know
Contains commands that delete or overwrite — references/release-notes-v0.12.0.md line 121; Contains commands that delete or overwrite — references/release-notes-v0.13.0.md line 106; Contains commands that delete or overwrite — references/release-notes-v0.13.1.md line 72. Read 2026-10-05, commit 152cfd9.
references/release-notes-v0.12.0.md, line 121 ↗references/release-notes-v0.13.0.md, line 106 ↗references/release-notes-v0.13.1.md, line 72 ↗Recently maintained
Its repository has had changes recently.
How we know
Last push to backnotprop/plannotator: 2026-10-05 (0 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from backnotprop
All from this publisher →- plannotator
Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant…
- plannotator-compound
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt…
- plannotator-setup-goal
Turn an idea or objective into a goal package for /goal.
- plannotator-visual-explainer
Generate self-contained HTML visualizations with Plannotator theming.
- review-renovate
Review Renovate bot PRs that update GitHub Actions dependencies.