skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
eljun/claude-workflow-skills81 installs

release

Use this skill when one or more ready-to-ship tasks have been merged and the user wants a versioned release. Generates changelog entries, creates tags or release notes, and moves merged tasks to Shipped.

How do I install this agent skill?

npx skills add https://github.com/eljun/claude-workflow-skills --skill release
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill automates the release process by reading task information and updating changelogs and git tags. It is generally safe, but it lacks specific sanitization for the task descriptions it processes, making it theoretically susceptible to indirect prompt injection if task files contain malicious instructions.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

release - Versioning Stage

Invariants

  • Release only merged Ready To Ship tasks.
  • Close the loop: a task moves to Shipped only when its post-deploy checks (listed in the PR / test report) have been run against the live system and their results recorded in the test report, or when the user explicitly waives them for that task. Merged is not the same as working.
  • Keep changelog entries user-focused.
  • Do not include unmerged pull requests.
  • Do not rewrite existing tags without explicit user approval.
  • After moving released items to Shipped, re-read TASKS.md to confirm each row left Ready To Ship. A stale tracker blocks downstream and headless sessions.

Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is release.

Invocation

Supported version inputs:

  • auto or no argument: derive from task Version Impact
  • patch
  • minor
  • major
  • explicit version such as v1.2.3

Workflow

  1. Read AGENTS.md.
  2. Read TASKS.md and find merged items in Ready To Ship.
  3. Read each task document for type, version impact, and summary.
  4. For each task, confirm its post-deploy checks were run and recorded (or waived by the user). Keep any task whose checks are still pending in Ready To Ship, and list it in the handoff with the pending checks.
  5. Determine the next version.
  6. Generate or update docs/changelogs/CHANGELOG.md.
  7. Commit changelog changes if the repository workflow expects release commits.
  8. Create a git tag when appropriate.
  9. Create release notes using the available repository hosting tool when appropriate.
  10. Move released items to Shipped in TASKS.md, removing each row from Ready To Ship.
  11. Re-read TASKS.md and verify the released task rows are in Shipped and absent from Ready To Ship. If any row is not in the expected section, the move was missed — perform the edit now before handoff.

Version Calculation

SignalVersion Impact
Breaking change or required user migrationmajor
New featureminor
Bug fix, docs, chore, small enhancementpatch

Highest impact wins when multiple tasks are released together.

Changelog Template

## [v{version}] - {Date}

### New Features
- {User-facing feature}

### Fixes
- {Bug fix}

### Improvements
- {Enhancement}

### Documentation
- {Documentation update}

### Breaking Changes
- {Required migration, if any}

Handoff

Release prepared: v{version}
Tasks shipped: {IDs}
Held (post-deploy checks pending): {IDs or "None"}
Changelog: docs/changelogs/CHANGELOG.md

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/eljun/claude-workflow-skills/release">View release on skillZs</a>