release

Create semantic version tags from changelogs and push them to Git.

28|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/AndrewDryga/coop --skill release-andrewdryga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/AndrewDryga/coop/tree/main/.agent/skills/release
Command: npx skills add https://github.com/AndrewDryga/coop --skill release-andrewdryga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually tagging, releasing, and promoting new software versions can be a time-consuming and error-prone process. This Skill automates and standardizes these steps, ensuring versions are bumps are correctly handled and tagged.

Core Features & Use Cases

  • Automated Version Bump: Automatically derive and apply semantic version tags based on the change log.
  • Tagging & Promotion: Pushes tags to the version control system and promotes them to a GitHub Release.
  • Validation & Security: Prevents no-op releases and ensures code changes are present before creating new tags.
  • Use Case: Use this Skill in a CI/CD pipeline to automatically create a new release each time a commit is made to the 'main' branch with real code changes.

Quick Start

Run 'coop release [version]' to cut a release. Omit the version to auto-determine from the change log.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semantic versioning in a CI/CD pipeline?

Automate semantic versioning by integrating a release script into your CI/CD pipeline that derives version bumps from the change log and pushes tags to GitHub. This ensures consistent, automated release workflows triggered by code changes.

How does automated release tagging determine the next version number?

Automated release tagging derives the next semantic version by analyzing the change log. When you omit the version argument, the script auto-detects the appropriate bump to apply and push.

What's the best way to prevent empty releases when automating GitHub tags?

Prevent empty releases by using a release automation script that validates code changes before creating new tags. This ensures no-op releases are blocked and tags are only pushed when real changes are present.

Do I need special Git permissions to push automated semantic version tags?

Yes, you need Git and GitHub permissions to push tags and promote them to a GitHub Release. The release automation requires these permissions to successfully push semantic version tags to your repository.

How do I cut a release with an auto-detected semantic version bump?

Cut a release with an auto-detected version by running the release command without specifying a version number. The script automatically determines the semantic version bump from the change log and pushes the tag.