baekenough/omcustom-release-notes

Release Notes Generator

Generate structured release notes directly within the Claude Code session, using git history and GitHub issues. No external API calls needed — Claude Code itself analyzes and generates the notes.

Purpose

Replaces the CI-based release-notes.yml workflow that previously used Claude API (ANTHROPIC_API_KEY). The release notes are now generated in-session and passed directly to gh release create --notes.

Usage

/omcustom-release-notes 0.36.0
/omcustom-release-notes 0.36.0 --previous-tag v0.35.3

Workflow

Phase 1: Gather Context

# 1. Determine previous tag
PREV_TAG=$(git tag --sort=-version:refname | grep -v "^v${VERSION}$" | head -1)

# 2. Get commit history
git log ${PREV_TAG}..HEAD --pretty=format:"%h %s"

# 3. Get changed files
git diff --name-status ${PREV_TAG}..HEAD

# 4. Get closed issues since previous tag
gh issue list --state closed --search "closed:>$(git log -1 --format=%ci ${PREV_TAG} | cut -d' ' -f1)" --json number,title,labels

Phase 2: Classify Changes

Categorize commits using Conventional Commits:

| Prefix | Category | Emoji | |--------|----------|-------| | feat: | Features | :rocket: | | fix: | Bug Fixes | :bug: | | docs: | Documentation | :books: | | refactor: | Refactoring | :recycle: | | test: | Tests | :test_tube: | | chore: | Chores | :wrench: | | security | Security | :lock: |

Phase 3: Generate Notes

Output format:

# Release v{VERSION}

## Highlights
(1-3 key features/changes)

## :rocket: Features
- **{title}** (#{issue}): {description}

## :bug: Bug Fixes
- **{title}** (#{issue}): {description}

## :lock: Security
- {security changes}

## :books: Documentation
- {doc changes}

## :recycle: Other Changes
- {other changes}

## Resource Changes
| Resource | Before | After | Delta |
|----------|--------|-------|-------|
| Rules | {n} | {n} | {delta} |
| Skills | {n} | {n} | {delta} |
| Agents | {n} | {n} | {delta} |

## Breaking Changes
{if any, otherwise omit section}

---
_Release notes generated with Claude Code_

Phase 4: Apply

The generated notes can be:

1. Direct: Passed to gh release create --notes "{notes}"
2. File: Written to release_notes.md for review before use
3. Update: Used with gh release edit v{VERSION} --notes "{notes}"

Integration

This skill is designed to be used during the release process:

/omcustom:npm-version patch|minor|major  ->  version bump
/omcustom-release-notes {version}         ->  generate notes
mgr-gitnerd: gh release create           ->  create release with notes

Notes

• No external API keys required
• Uses git history and gh CLI for data gathering
• Claude Code analyzes and generates notes in-context
• Resource count changes auto-detected from CLAUDE.md history