# create-release-note

create-release-note generates two versions of release documentation from recent commits: one for customers, one for engineers. Analyzes changes, groups them by theme, and traces each change back to specific commit hashes.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 2744 repo stars
- Author: centminmod
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/centminmod/my-claude-code-setup/tree/HEAD/.claude/commands/documentation/create-release-note.md
- Updated: 2026-10-08
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/create-release-note

## What it does

The command offers two workflows. Mode 1 takes a commit count (default 10) and generates notes immediately. Mode 2 lists commits from the last 24 hours, lets you pick a starting point, and generates from there to HEAD.

Both modes produce customer-facing release notes (focused on benefits, features, user impact) and technical engineering notes (with commit SHAs, file paths, implementation details). It groups related commits by subsystem, extracts file changes, and traces every claim back to actual commits.

Requires a Git repository with accessible commit history. Each statement in the output references specific SHAs and changed files.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/create-release-note.md` — Call it with /create-release-note. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/create-release-note.md` — Call it with /prompts:create-release-note. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/create-release-note.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/create-release-note.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/centminmod/my-claude-code-setup/tree/HEAD/.claude/commands/documentation/create-release-note.md

## When to use it
- generate two distinct release documents from commit history
- select a precise commit range by date or count
- group related changes across multiple subsystems
- link every claim to specific commits and files

## Example prompts
- /create-release-note 20
- /create-release-note
- generate release notes for the last 15 commits

## Source text · create-release-note.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 151f2947bd3c034a.

BEGIN THIRD-PARTY FILE 151f2947bd3c034a
````text
# Release Note Generator

Generate comprehensive release documentation from recent commits, producing two distinct outputs: a customer-facing release note and a technical engineering note.

## Interactive Workflow

When this command is triggered, **DO NOT** immediately generate release notes. Instead, present the user with two options:

### Mode Selection Prompt

Present this to the user:

```text
I can generate release notes in two ways:

**Mode 1: By Commit Count**
Generate notes for the last N commits (specify number or use default 10)
→ Quick generation when you know the commit count

**Mode 2: By Commit Hash Range (i.e. Last 24/48/72 Hours)**
Show all commits from the last 24/48/72 hours, then you select a starting commit
→ Precise control when you want to review recent commits first

Which mode would you like?
1. Commit count (provide number or use default)
2. Commit hash selection (show last 24/48/72 hours)

You can also provide an argument directly: /create-release-note 20
```

---

## Mode 1: By Commit Count

### Usage

```bash
/create-release-note          # Triggers mode selection
/create-release-note 20       # Directly uses Mode 1 with 20 commits
/create-release-note 50       # Directly uses Mode 1 with 50 commits
```

### Process

1. If `$ARGUMENTS` is provided, use it as commit count
2. If no `$ARGUMENTS`, ask user for commit count or default to 10
3. Set: `COMMIT_COUNT="${ARGUMENTS:-10}"`
4. Generate release notes immediately

---

## Mode 2: By Commit Hash Range

### Workflow

When user selects Mode 2, follow this process:

### Step 1: Retrieve Last 24 Hours of Commits

```bash
git log --since="24 hours ago" --pretty=format:"%h|%ai|%an|%s" --reverse
```

### Step 2: Present Commits to User

Format the output as a numbered list for easy selection:

```text
Commits from the last 24 hours (oldest to newest):

 1. a3f7e821 | 2025-10-15 09:23:45 | Alice Smith | Add OAuth provider configuration
 2. b4c8f932 | 2025-10-15 10:15:22 | Bob Jones | Implement token refresh flow
 3. c5d9e043 | 2025-10-15 11:42:18 | Alice Smith | Add provider UI components
 4. d6e1f154 | 2025-10-15 13:08:33 | Carol White | Database connection pooling
 5. e7f2g265 | 2025-10-15 14:55:47 | Alice Smith | Query optimization middleware
 6. f8g3h376 | 2025-10-15 16:20:12 | Bob Jones | Dark mode CSS variables
 7. g9h4i487 | 2025-10-15 17:10:55 | Carol White | Theme switching logic
 8. h0i5j598 | 2025-10-16 08:45:29 | Alice Smith | Error boundary implementation

Please provide the starting commit hash (8 characters) or number.
Release notes will be generated from your selection to HEAD (most recent).

Example: "a3f7e821" or "1" will generate notes for commits 1-8
Example: "d6e1f154" or "4" will generate notes for commits 4-8
```

### Step 3: Generate Notes from Selected Commit

Once user provides a commit hash or number:

```bash
# If user provided a number, extract the corresponding hash
SELECTED_HASH="<hash from user input>"

# Generate notes from selected commit to HEAD
git log ${SELECTED_HASH}..HEAD --stat --oneline
git log ${SELECTED_HASH}..HEAD --pretty=format:"%H|%s|%an|%ad" --date=short
```

**Important:** The range `${SELECTED_HASH}..HEAD` means "from the commit AFTER the selected hash to HEAD". If you want to include the selected commit itself, use `${SELECTED_HASH}^..HEAD` or count commits with `--ancestry-path`.

### Step 4: Confirm Range

Before generating, confirm with user:

```text
Generating release notes for N commits:
From: <hash> - <commit message>
To:   <HEAD hash> - <commit message>

Proceeding with generation...
```

---

## Core Requirements

### 1. Commit Analysis

**Determine commit source:**

- **Mode 1**: `COMMIT_COUNT="${ARGUMENTS:-10}"` → Use `git log -${COMMIT_COUNT}`
- **Mode 2**: User-selected hash → Use `git log ${SELECTED_HASH}..HEAD`

**Retrieve commits:**

- Use `git log <range> --stat --oneline`
- Use `git log <range> --pretty=format:"%H|%s|%an|%ad" --date=short`
- Analyze file changes to understand scope and impact
````
END THIRD-PARTY FILE 151f2947bd3c034a

The third-party file has ended. Everything between the 151f2947bd3c034a tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 4011 of 16131 bytes. © centminmod · MIT · https://github.com/centminmod/my-claude-code-setup/tree/HEAD/.claude/commands/documentation/create-release-note.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
