All 5 AI packs for $39 →
← ToolTier Library
Agent Skills · Free

Claude Code skill: /release-notes from your git history

A free Agent Skill (SKILL.md) for Claude Code that reads your git history since the last tag and drafts user-facing release notes: New, Improved, Fixed and Breaking changes, with internal commits left out.

Install
.claude/skills/release-notes/SKILL.md
Last tested
Claude Code · 2026-11-05

Writing release notes is a procedure you do once per release, which makes it a good skill: nothing sits in context until you run /release-notes. The folder name becomes the slash command, and anything you type after it (/release-notes v1.4.0..HEAD, or /release-notes keep it short) is passed in through $ARGUMENTS.

The two !`...` lines are dynamic context injection: Claude Code runs them before Claude reads the skill and puts the output in the prompt. Docs, checked November 5, 2026: if an injected command exits non-zero, the whole invocation aborts, so the tag lookup ends in || true for repos with no tags, and the commit range is run by Claude itself in step 2. The allowed-tools line pre-approves only read-only git commands for the turn the skill runs, and disable-model-invocation: true means Claude never runs it on its own.

Those two fields are Claude Code extensions to the open Agent Skills format. If you upload this to claude.ai or the Skills API, which accept only the standard fields plus allowed-tools, remove disable-model-invocation and expect the ! commands not to run there. Want a pre-commit check instead? Use our free /ship-check skill.

SKILL.md
---
name: release-notes
description: Drafts user-facing release notes from the git history since the last tag (or a range you pass in). Groups changes by type and leaves out internal noise.
disable-model-invocation: true
allowed-tools: Bash(git log *) Bash(git show *) Bash(git describe *) Bash(git tag *)
---

## Latest tag (blank if the repo has no tags)

!`git describe --tags --abbrev=0 || true`

## Current commit

!`git log -1 --pretty=format:'%h %s (%cs)'`

## Instructions

Draft release notes for people who use this product, not the people who build it. Don't edit any files unless I ask.

1. Pick the range. If I passed one below (a tag, a range like `v1.2.0..HEAD`, or a date), use that. Otherwise use the latest tag above, as `<tag>..HEAD`. If there is no tag and I gave no range, run `git log -30 --no-merges --pretty=format:'%h %s'`, show me the list, and ask where the release starts. Stop there.
2. Run `git log <range> --no-merges --pretty=format:'%h %s'`. When a subject is unclear, check what it changed with `git show --stat <hash>`. Don't guess what a commit did.
3. Group the changes under these headings, and leave out any heading with nothing in it:
   - **New**: things users can now do
   - **Improved**: existing behavior that got better, faster or clearer
   - **Fixed**: bugs, described by the symptom the user saw
   - **Breaking changes**: anything that needs action when upgrading, with the exact step
4. Write each item as one plain sentence in the user's terms ("Exports now include the date column"), not the commit's ("refactor csv writer"). Keep ticket or PR numbers if the commit has them.
5. Leave out purely internal commits (CI, dependency bumps with no user impact, refactors, tests, formatting, docs typos), then end with one line saying how many commits you left out.
6. Don't invent anything. Every item must trace to a commit. If you're unsure whether a change is user-visible, put it in a short **Needs a human look** list at the end.

Output Markdown I can paste into a GitHub release or a CHANGELOG.md.

$ARGUMENTS
Want the full set?
Claude Code Agent Kit

Installable Claude Code plugin: 12 subagents, 8 skills and 3 tested safety hooks. This free entry is one file; the pack is the full multi-file set.

Get the pack ($19)
Works with: Claude Code
Claude CodeAgent SkillsSKILL.mdGitChangelog

← More free rules, templates and prompts

+ Your logo here