Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →odradekai/releasing
Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness
Passed 14 of 21 test cases with the skill, and 10 of 21 without it.
and 4 more in the full report
6 fixed9 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
During Step 2 of releasing `./plugins/logger`, pre-flight audit found several quality findings. What subsystem should be invoked to orchestrate fixes?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes bundles-forge:optimizing. | Missed | Passed |
The instructions your model reads when the skill loads.
Orchestrate the complete release workflow for a bundle-plugin: verify quality, scan for security risks, check documentation consistency, review change coherence, test locally, bump versions, update documentation, and publish to target platforms.
Core principle: Release is a checkpoint, not a formality. Every release deserves the full pipeline — even "minor" version bumps can introduce drift or break platform installs. Users should complete all agent, skill, and workflow development before invoking this skill.
Skill type: Rigid — follow every step exactly. Releases have no room for improvisation.
For version management infrastructure details (.version-bump.json schema, script usage, version setup for new projects), read references/version-infrastructure.md. For distribution strategy options, read references/distribution-strategy.md.
Announce at start: "I'm using the releasing skill to prepare this project for release."
| Context | Path |
|---|---|
| User wants to release a version, provides a project directory | Path 1: Standard release — run the full pipeline below |
| Urgent fix with small changes | Path 2: Hotfix release — run the abbreviated pipeline (see Hotfix Releases) |
| Project needs version infrastructure for the first time | Path 3: Version setup — read references/version-infrastructure.md § Version Setup |
0. Prerequisites → 1. Pre-flight Checks → 2. Address Findings
→ 3. Change Review & Doc Sync → 4. Local Testing
→ 5. Version Bump → 6. Release Notes
→ 7. Final Verification → 8. Publish
Verify all conditions before entering the pipeline. Hard requirements block the pipeline; soft requirements trigger warnings.
Hard requirements (must pass):
skills/ directory and package.json)git status shows no uncommitted or unstaged changes. All development work (agents, skills, workflows) must be committed before releasing.test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.