Have Autohand Code inspect commits, PR titles, changed files, and product surfaces to draft release notes.
Turn git history into a useful changelog
Delivery Delivery and operations Release Workflow
autohand -p "Draft release notes from the commits since the last tag"
A grouped release note draft with customer-facing language and technical details.
Automate release notes with Autohand Code is a release workflow that turns commits, PRs, changed files, docs updates, and issue references into grouped customer-facing release notes. ### At a glance | Question | Answer | | --- | --- | | Best for | tagging a release, briefing support, writing changelogs, or preparing launch notes | | Primary inputs | Previous tag, release branch, or date range; Audience such as customers, developers, support, or internal operations; Items to exclude, highlight, or call out as risky | | Autohand Code returns | A grouped release note draft with customer-facing language and technical details. | | Avoid when | the branch history is noisy and product owners have not named what shipped | ### How Autohand Code handles this workflow 1. Reads commits, PR titles, file changes, issue references, and docs edits. 2. Groups changes by customer impact, fixes, docs, and internal work. 3. Removes commit-message noise and avoids unsupported claims. 4. Returns migration notes, rollout risks, and copy ready for review. ### Best inputs - Previous tag, release branch, or date range - Audience such as customers, developers, support, or internal operations - Items to exclude, highlight, or call out as risky ### Strong prompt autohand -p "Draft release notes from the commits since the last tag" ### Autohand Code CLI options - Run `git log --oneline <last-tag>..HEAD | autohand -p "Draft release notes grouped by customer impact"` for a fast draft. - Use `autohand -p "Draft release notes from the commits since the last tag"` when Autohand should inspect files as well as commit titles. - Use `AUTOHAND_NON_INTERACTIVE=1` in release scripts when the notes draft runs as part of CI. ### Review before accepting Check that every shipped claim maps to a commit, PR, file change, or release artifact. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Automate release notes with Autohand Code? Automate release notes with Autohand Code is a release workflow that turns commits, PRs, changed files, docs updates, and issue references into grouped customer-facing release notes. ### When should a team use Automate release notes? Use it when the git history is real but the story needs product language. ### What evidence should reviewers check for Automate release notes? Check that every shipped claim maps to a commit, PR, file change, or release artifact.
Tutorial Automate Release Notes from Git History Turn commits and PRs into customer-facing release notes. /docs/tutorials/automate-release-notes.html Guide Git Flow Automation Connect release notes to branching, tagging, and review flow. /docs/guides/git-flow-automation.html Reference CLI Reference Find CLI commands and flags used in release workflows. /docs/working-with-autohand-code/cli-reference.html