release

Automate release PR creation with semver calculation and changelog generation.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Codagent-AI/agent-skills --skill release-codagent-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Codagent-AI/agent-skills/tree/main/.agents/skills/release
Command: npx skills add https://github.com/Codagent-AI/agent-skills --skill release-codagent-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, git, and includes scripts (resource) components.

What problem does it solve?

Manually creating release pull requests is time-consuming and error-prone, requiring teams to track merged changes, calculate semantic version bumps, write changelog entries, update version numbers across multiple plugin manifests, and draft the PR itself. This Skill eliminates all that manual work for projects using the Codagent agent skills bundle.

Core Features & Use Cases

  • Automated PR Gathering: Collects all merged PRs since the last release tag, plus any unmerged changes on the current working branch if applicable.
  • Semver Calculation: Determines the correct version bump (major/minor/patch) based on conventional commit prefixes and breaking change labels.
  • Changelog Generation: Creates formatted, grouped changelog entries sorted by PR number, with expanded descriptions for clarity.
  • Multi-Platform Version Sync: Updates version numbers across all host-specific plugin manifests (Claude Code, Codex, Cursor) and the marketplace configuration file.
  • Use Case: A team shipping a new version of their Codagent plugin can run this Skill to generate a complete release PR in seconds, instead of spending 30+ minutes on manual tracking and file updates.

Quick Start

Use the release skill to create a new release PR for the latest merged changes to the agent-skills repository.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate release PRs and changelog generation for conventional commits?

You can automate release PRs and changelog generation by fetching merged GitHub pull requests, classifying changes by semver bump type, and creating structured changelog entries with updated version numbers in plugin manifests. This removes manual tracking and file updates entirely.

How does semver calculation work from conventional commit prefixes?

Semver calculation determines the correct version bump (major, minor, or patch) by analyzing conventional commit prefixes and breaking change labels from merged pull requests. It automatically classifies each change to decide the appropriate semantic version increment.

Can I synchronize version bumps across multiple plugin manifests on different platforms?

Yes, you can synchronize version bumps across multiple host-specific plugin manifests, including Claude Code, Codex, and Cursor configurations, alongside the marketplace configuration file. This ensures all platform versions stay aligned during a release.

What's the best way to create a release workflow for a multi-platform plugin bundle?

The best way to create a release workflow for a multi-platform plugin bundle is to automate the end-to-end process: gather merged PRs, calculate semantic version bumps, generate grouped changelogs, update all manifests, and draft the release pull request automatically.

Do I need jq, gh, and git installed to automate the release workflow?

Yes, you need jq, gh, and git installed in your environment to automate the release workflow. These dependencies are required to fetch GitHub PR data, parse JSON outputs, and interact with the repository for version tagging and PR creation.

Why does my automated changelog entry not include unmerged changes on the working branch?

Automated changelog generation primarily collects merged pull requests since the last release tag. It also includes unmerged changes on the current working branch if applicable, but correct generation requires conventional commit prefixes to classify and group entries properly.