- Home
- Skills
- DevOps & Cloud
- git release automation lite
Works with the AI tools you already use
git release automation lite
Automates changelog generation, semver suggestions, and release readiness checks from Git commit history — read-only and structured for real release workflows.
Free
git release automation lite
Example session with this skill installed
Generate a full release package for range v1.3.0..HEAD (current version 1.3.0). Classify this git log, flag breaking changes with migration hints, suggest the next semver, and give a READY / READY-WITH-NOTES / NEEDS-REVIEW verdict.
[paste git log here]
- Read your context and instructions
- Compiled the git release automation
Release Package
1. Summary
| Field | Value |
|---|---|
| Range | v1.3.0..HEAD |
| Total commits | 8 |
| Suggested version | 2.0.0 (major) |
| Breaking changes | 1 |
| Release readiness | READY-WITH-NOTES |
2. Changelog (Keep-a-Changelog)
Added
- Dark mode toggle.
Changed
- BREAKING: Auth endpoint
/auth/loginresponse shape changed.
Fixed
- Resolved a crash on empty cart.
- Handled null coupon codes at checkout.
3. Release Notes (human-friendly)
Dark mode is here — plus a cleaner, more reliable checkout.
Highlights
- You can now switch the whole app to dark mode with a single toggle.
- Checkout is more robust: empty carts no longer crash; missing coupon codes are handled safely.
Breaking change for API consumers
/auth/login now returns { token, expiresIn } instead of { token }.
4. Breaking Changes & Migration
| Change | Impact | Migration hint |
|---|---|---|
/auth/login response shape | API clients expecting { token } only | Update clients to read `tok |
5. Release Readiness Checklist
| Item | Status | Notes |
|---|---|---|
| Breaking changes documented | done | Migration hint provided |
| Version determined | done | 2.0.0 (major) |
| Changelog complete | done | |
| Release notes written | done | |
| Tests passing | needs-manual-check | Verify CI is green |
| Rollback plan identified | needs-manual-check | Confirm rollback steps |
6. Needs Attention
- Breaking change requires coordinated communication to API consumers.
7. Release JSON
{
"range": "v1.3.0..HEAD",
"total_commits": 8,
"version": { "current": "1.3.0", "suggested": "2.0.0", "bump_type": "major" },
"release_readiness": "READY-WITH-NOTES",
"counts": { "features": 2, "fixes": 2, "breaking": 1, "reverts": 0, "noise_excluded": 3, "flagged_risky": 0 }
}
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Manually drafting changelogs from raw git logs is tedious and easy to get wrong. Maintainers often miss breaking changes, mix technical noise with user-facing notes, and guess at the next semver bump.
What it does
- Classifies commits into Keep-a-Changelog sections (Added, Changed, Deprecated, Removed, Fixed, Security)
- Detects breaking changes and drafts migration hints
- Suggests the next semver bump (major / minor / patch) from commit intent
- Produces a release readiness checklist with a READY / READY-WITH-NOTES / NEEDS-REVIEW verdict
- Outputs a full package: technical changelog, human-friendly release notes, and CI-ready JSON
Frameworks & tools
Works with any Git-based project. Best with Conventional Commits; unstructured history is handled with best-effort classification. Accepts a commit range, pasted git log, or PR titles. Compatible with Claude Code, Cursor, Codex CLI, Gemini CLI, VS Code Copilot, and other SKILL.md agents.
Why this beats prompting it yourself
Built-in rules flag WIP/HACK/DRAFT commits, apply hard readiness gates, keep noise (chore/test/ci) out of user notes, and enforce a consistent JSON schema for downstream use — so every release package looks the same.
Use cases
- Draft GitHub/GitLab release descriptions from a tag range
- Spot breaking changes and migration paths before merge or ship
- Produce weekly change summaries for product stakeholders
- Suggest the next version number (and export JSON) for human- or CI-driven releases
Known limitations
Strictly read-only — does not push, tag, commit, merge, checkout, or publish. Single-package focus; not for complex monorepo orchestration. Cannot verify tests, docs updates, or rollback plans (those stay needs-manual-check). Semver is a suggestion only; a human or your CI must apply the bump. Best results with Conventional Commits; unstructured history is best-effort.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
7 people have installed this skill.
Trust & safety
Security scanned
Verified clean 1 month ago
- Free to download with an account