release_skill

Overview

This skill automates creating a new specops release by guiding a version bump, tagging the repo, and publishing a GitHub release. It standardizes updates across install scripts, README install URLs, and the plugin manifest so releases are consistent and repeatable. Use it to produce clean release notes and push tags and releases with the GitHub CLI.

How this skill works

The skill inspects the current git tag to suggest a semver bump (patch/minor/major), updates version literals in install.ps1, install.sh, README.md, and .claude-plugin/plugin.json, then commits those changes. It creates and pushes a matching git tag, gathers commits since the previous tag to generate release notes, and calls gh release create to publish the GitHub release. PowerShell strings and escaping are handled according to platform conventions.

When to use it

• When preparing a new specops release and you need to bump the version consistently.
• When you want to generate consolidated release notes from commits since the last tag.
• When you need to update install scripts and README install URLs to the new tag.
• When you plan to publish a tagged GitHub release using the GitHub CLI.
• Before merging breaking changes that require a major version bump.

Best practices

• Follow semver: bump patch for fixes, minor for features, major for breaking changes.
• Verify current version with git describe --tags --abbrev=0 before selecting a new version.
• Update install.ps1 (v-prefixed), install.sh (v-prefixed), README install URLs, and .claude-plugin/plugin.json (no v prefix).
• Run git log $(git describe --tags --abbrev=0 HEAD^)..HEAD --oneline to craft concise release notes.
• Ensure the tag name matches versions in scripts, README, and plugin.json before pushing.
• Use gh release create with a clear title and the RELEASE_NOTES_HERE section formatted for users.

Example use cases

• You finished a set of bug fixes and want to publish v1.2.3 as a patch release with notes.
• You merged a new feature branch and need to publish v1.3.0 with updated install URLs.
• You introduced breaking API changes and must release v2.0.0 and update plugin.json without the v prefix.
• You want an automated checklist to ensure all version locations and the tag are consistent before pushing.