release

Generates a semver release PR with a grouped CHANGELOG entry from conventional commits.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill release-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/release
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill release-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cutting a release by hand means reading the commit log, deciding a semver bump, writing a CHANGELOG entry, and opening a release PR — a repetitive, error-prone process that is easy to get wrong. ## Core Features & Use Cases - Automatic semver detection: Reads conventional commits since the last tag and proposes a MAJOR, MINOR, or PATCH bump, with an option to override. - Agent-generated CHANGELOG: Groups commits into Added, Fixed, Changed, and Breaking sections and prepends the entry to CHANGELOG.md after user review. - Release PR automation: Creates a release/vX.Y.Z branch, commits the changelog, pushes it, and opens a PR targeting main via the GitHub CLI. - Use Case: After merging several feature branches, run the skill with --dry-run to preview the proposed version and changelog, then execute it to open a release PR without touching git commands manually. ## Quick Start Ask the assistant to cut a new release from the current branch, for example by saying: run the release skill with --dry-run to preview the next version and changelog.

Frequently Asked Questions about release

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

FAQPage Schema
How do I create a GitHub release from conventional commits?▼

Run the release skill on your feature branch. It reads commits since the last tag, proposes a semver bump based on conventional-commit types, drafts a grouped CHANGELOG entry, and opens a release PR targeting main.

How is the semver version bump determined automatically?▼

The bump follows conventional-commit types: any breaking marker (!) triggers MAJOR, feat commits trigger MINOR, and only fix, chore, docs, or similar types trigger PATCH. You can override the proposal or pass an explicit version like v1.2.0.

Can I preview the release without changing any files?▼

Yes, pass --dry-run to print the proposed version, the drafted CHANGELOG section, and the PR body without creating branches, commits, pushes, or pull requests.

Does the release skill work on any GitHub repository?▼

Yes, it makes no framework-specific assumptions. It only requires git, the GitHub CLI (gh), a clean working tree, and a current branch that is ahead of main and is not main itself.

Why does the release skill refuse to run on my branch?▼

It refuses when the working tree has uncommitted changes, the branch has no commits ahead of main, or the current branch is main itself. Commit or stash changes and run from a feature branch.

Does the release skill merge the PR or create the git tag?▼

No, it stops after opening the release PR. Merging stays with the reviewer, and the tag is created on main after merge, either manually with git tag or via a CI workflow.