Skip to content
Back to skills

Git Release

ASecurity

Create consistent releases and changelogs from merged PRs. Proposes semantic version bump, drafts release notes, and provides a copy-pasteable release command.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsgobashgitapici/cdsecurityperformancedocumentation

Works with

  • api

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add alisattorov06/ali-kiro --skill git-release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Release?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Release
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alisattorov06-git-release/badge)](https://www.skillsdirectory.com/skills/alisattorov06-git-release)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-release
description: Create consistent releases and changelogs from merged PRs. Proposes semantic version bump, drafts release notes, and provides a copy-pasteable release command.
origin: FlowDeck
---

# Git Release Skill

Creates releases with consistent versioning, accurate changelogs, and proper tagging.

## When to Activate

Activate when:
- A release is complete and ready to ship
- You need to cut a release tag
- You need to generate a CHANGELOG entry

## Core Principles

- Semver strictly: major.minor.patch
- Conventional commits drive the version bump automatically
- Changelog is for humans: group by type, use plain language
- One release per tag — no force-pushing tags

## Workflow

1. **Collect commits** — `git log [last-tag]..HEAD --oneline`
2. **Determine version bump** from commits:
   - Breaking change (`!` or `BREAKING CHANGE:`) → major bump
   - `feat:` → minor bump
   - `fix:`, `refactor:`, `perf:` → patch bump
   - `docs:`, `test:`, `chore:` → no version bump (unless last release)
3. **Draft changelog** — group commits by type
4. **Update CHANGELOG.md** — prepend new version under `## Unreleased`
5. **Tag and push** — provide the exact commands

## Conventional Commits Types

| Type | Version Bump | Description |
|------|-------------|-------------|
| `feat` | minor | New feature |
| `fix` | patch | Bug fix |
| `perf` | patch | Performance improvement |
| `refactor` | patch | Code change, no behavior change |
| `docs` | none | Documentation only |
| `test` | none | Adding or updating tests |
| `chore` | none | Maintenance, dependencies |
| `ci` | none | CI/CD configuration |
| `feat!` or `BREAKING CHANGE:` | major | Breaking API change |

## Changelog Format

Follow Keep a Changelog (keepachangelog.com):

```markdown
## [1.2.0] — 2024-01-15

### Added
- User authentication via JWT (feat: add JWT auth)
- Password reset via email (feat: add password reset)

### Fixed
- Token expiry calculation was off by one day (fix: correct token expiry)

### Changed
- Migrated from bcrypt to argon2 for better security (refactor: use argon2)
```

## Release Commands

```bash
# After updating CHANGELOG.md
git add CHANGELOG.md
git commit -m "chore(release): v1.2.0"
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags
```

## Output Format

```markdown
## Release Proposal: v[X.Y.Z]

**Version bump**: patch | minor | major
**Reason**: [breaking change / new feature / bug fix]

### CHANGELOG entry (copy into CHANGELOG.md):
[formatted changelog section]

### Release commands:
```bash
[copy-pasteable commands]
```
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.