release

Bump versions across install scripts and create GitHub releases with release notes.

2|Updated Jan 19, 2026

Search Tags:#git #versioning #github #release #semver #release-notes

Ready to run

npx skills add https://github.com/wilddeer/specops --skill release-wilddeer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/wilddeer/specops/tree/main/.claude/skills/release
Command: npx skills add https://github.com/wilddeer/specops --skill release-wilddeer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release process for specops by handling version bumps, Git tags, and GitHub releases to ensure consistent releases.

Core Features & Use Cases

Version bumping across install.ps1, install.sh, README.md, and plugin.json
Tag creation and publishing to GitHub
Release notes generation from commit history
Suitable for CI/CD pipelines and manual releases

Quick Start

Create a new release by bumping the version and letting the workflow handle tagging and GitHub release.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate version bumps and GitHub releases for my project?▼

Automating version bumps and GitHub releases requires updating version references across install scripts, README, and plugin.json, then tagging the release and creating a GitHub release. This workflow supports standard semver versioning and can run in CI/CD pipelines or manually.

What is the best way to generate release notes from commit history?▼

Generating release notes from commit history involves parsing commits since the last Git tag to automatically compile changes. This approach ensures consistent release notes for your GitHub releases without manual summarization.

How do I ensure version consistency across install scripts and plugin files?▼

Ensuring version consistency across install scripts and plugin files requires simultaneously bumping version references in install.ps1, install.sh, README.md, and plugin.json. This prevents version mismatch errors during your release process.

Can I use standard semver versioning to tag and publish releases in CI/CD?▼

Yes, you can use standard semver versioning to tag and publish releases in CI/CD. The workflow pushes the new tag to main and creates the GitHub release automatically, fitting both automated pipelines and manual workflows.

Does the release process update version references in install.sh and install.ps1?▼

Yes, the release process updates version references in install.sh and install.ps1. It also updates README.md and plugin.json to ensure complete version consistency before tagging and publishing the GitHub release.