skills.rest
YuriiYInno
YuriiYInnoCOMMUNITY
Explore all skills by this author →
GitHub

release

Create GitHub releases with automated changelog generation from conventional git commits.

Updated Oct 2, 2025
Search Tags:#changelog#conventional commits#semantic versioning#git tags#release automation#github release
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill release-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/release
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill release-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Manually writing changelogs, tagging versions, and publishing GitHub releases is repetitive and error-prone. This Skill automates the entire release workflow by analyzing commits since the last tag, categorizing them with conventional commit rules, updating CHANGELOG.md, and publishing the release. ## Core Features & Use Cases - Automated Commit Analysis: Collects commits since the last tag and categorizes them into Added, Changed, Fixed, Deprecated, Removed, and Security sections using a bundled Python script. - Semantic Versioning Guidance: Parses the last tag and prompts for patch, minor, or major version bumps with calculated suggestions. - Keep a Changelog Compliance: Generates changelog entries in the standard format with commit hashes and imperative mood, inserting them into CHANGELOG.md after user confirmation. - Use Case: After merging a sprint's worth of feature branches, run the release flow to generate a categorized changelog entry, tag v1.4.0, push to origin, and create the GitHub release in one guided workflow. ## Quick Start Create a new release for this repository with an auto-generated changelog from commits since the last tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I generate a changelog from git commits automatically?▼

Run the release workflow, which collects commits since the last tag using git log and categorizes them with the bundled categorize_commits.py script. Commits are grouped by conventional commit prefixes like feat, fix, and refactor into Keep a Changelog sections.

How to create a GitHub release from the command line?▼

Use the gh release create command with a version tag, title, and release notes. This Skill automates the full sequence: committing CHANGELOG.md, creating an annotated git tag, pushing to origin, and publishing the release with gh.

What conventional commit prefixes map to changelog categories?▼

feat maps to Added, fix to Fixed, refactor and perf to Changed, deprecate to Deprecated, remove to Removed, and security to Security. Commits with docs, build, ci, or chore prefixes are excluded from user-facing changelog sections.

What happens if my repository has no previous git tags?▼

The workflow falls back to the initial commit as the starting point for analysis. It then asks whether the first version should be v0.1.0 or v1.0.0 before generating the changelog entry.

Does the release workflow push changes without confirmation?▼

No. The workflow requires explicit user confirmation before writing CHANGELOG.md and again before committing, tagging, pushing to origin, and creating the GitHub release. Existing tags are checked to prevent overwriting.

Related Skills

Explore More Software Engineering Skills→
KosmoCHEKosmoCHE

squash

Consolidate commits on the current branch into a single Conventional Commits message.

Community
Intermediate
GenEducationGenEducation

ship

Prepare feature branches for release with tests, versioning, and pull requests.

Official
Advanced
ShiroiKuma0ShiroiKuma0
25

changelog

Update CHANGELOG.md with categorized user-facing release notes.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced