human-release-notes
Turns commits, a diff, or a technical change list into end-user release notes in three sections: New, Improved, and Fixed. Filters out purely internal changes (refactors, dependencies). Use when the user asks for "release notes", "changelog for users", or "what's new" built from commits, diffs, or change lists.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/plaf-labs--human-release-notes)HTML
<a href="/listings/plaf-labs--human-release-notes"><img src="/api/listings/plaf-labs--human-release-notes/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
`SKILL.md` is the only file the AI needs. It is plain Markdown with no tool-specific dependencies.
Any AI chat
Paste the contents of `SKILL.md` as the system prompt, custom instructions, or first message.
Coding agents and IDEs
Put `SKILL.md` where your tool reads project instructions:
| Tool | Location | | --------------------------------------------- | ------------------------------------------------------------------------------ | | Claude Code | `~/.claude/skills/human-release-notes/SKILL.md` (or project `.claude/skills/`) | | Codex, Gemini CLI, others reading `AGENTS.md` | Append contents to `AGENTS.md` | | Cursor | Copy into `.cursor/rules/human-release-notes.mdc` | | GitHub Copilot | Append contents to `.github/copilot-instructions.md` |
Claude Code, command line:
mkdir -p ~/.claude/skills/human-release-notes cp SKILL.md ~/.claude/skills/human-release-notes/
PowerShell:
New-Item -ItemType Directory -Force "$HOME\.claude\skills\human-release-notes" | Out-Null Copy-Item SKILL.md "$HOME\.claude\skills\human-release-notes\"
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 53 lines
- ---
- name: human-release-notes
- description: Turns commits, a diff, or a technical change list into end-user release notes in three sections: New, Improved, and Fixed. Filters out purely internal changes (refactors, dependencies). Use when the user asks for "release notes", "changelog for users", or "what's new" built from commits, diffs, or change lists.
- ---
- # human-release-notes
- ## Input
- Accept any of:
- - Commit list (`git log` output, pasted messages).
- - Diff (`git diff`, patch).
- - Hand-written technical change list.
- If the input is empty or does not show what changed for the user, ask for more context before writing.
- ## Steps
- 1. Read the full input.
- 2. Drop purely internal changes: refactors, dependency changes, internal renames, tests, CI, formatting, code cleanup, version bumps.
- 3. Rewrite each remaining change from the user's point of view: what they can do now, what looks different, what no longer fails. No function, file, module, or technical jargon names.
- 4. Assign each change to exactly one section:
- - **New**: functionality that did not exist before.
- - **Improved**: something that existed and now works better, faster, or clearer.
- - **Fixed**: a bug the user could notice that no longer happens.
- 5. If a change does not clearly fit a section, or it is unclear whether users can see it, ask before including it.
- ## Output format
- Write the output in neutral Latin American Spanish.
- ```
- ## Nuevo
- - ...
- ## Mejorado
- - ...
- ## Corregido
- - ...
- ```
- - One bullet per change, one sentence, plain language.
- - Omit empty sections.
- - No version header or date unless the user asks for one.
- - No closing or summary.
- ## Rules
- - Output language: neutral Latin American Spanish (es-419), unless the user asks for another language. Avoid regional slang (voseo, "vos", "ustedes" forms specific to one country).
- - Do not invent features or benefits that are not in the input.
- - If a commit mixes a visible change with an internal one, include only the visible part.
- - If unsure, ask before generating the final document. Ask at most three questions at a time.
README.md · README · 79 lines
- # human-release-notes — AI release notes & changelog generator (Spanish)
- Turn git commits and diffs into clear, user-facing release notes in Spanish (es-419) with any AI assistant: Claude Code, Cursor, GitHub Copilot, Codex or ChatGPT.
- A skill that turns commits, diffs, or technical change lists into end-user release notes. Works with any AI assistant.
- Output has three sections: **New**, **Improved**, and **Fixed**. Purely internal changes (refactors, dependency bumps, tests, CI) are filtered out.
- Output language: neutral Latin American Spanish (es-419). Input can be in any language.
- ## Install
- `SKILL.md` is the only file the AI needs. It is plain Markdown with no tool-specific dependencies.
- ### Any AI chat
- Paste the contents of `SKILL.md` as the system prompt, custom instructions, or first message.
- ### Coding agents and IDEs
- Put `SKILL.md` where your tool reads project instructions:
- | Tool | Location |
- | --------------------------------------------- | ------------------------------------------------------------------------------ |
- | Claude Code | `~/.claude/skills/human-release-notes/SKILL.md` (or project `.claude/skills/`) |
- | Codex, Gemini CLI, others reading `AGENTS.md` | Append contents to `AGENTS.md` |
- | Cursor | Copy into `.cursor/rules/human-release-notes.mdc` |
- | GitHub Copilot | Append contents to `.github/copilot-instructions.md` |
- Claude Code, command line:
- ```bash
- mkdir -p ~/.claude/skills/human-release-notes
- cp SKILL.md ~/.claude/skills/human-release-notes/
- ```
- PowerShell:
- ```powershell
- New-Item -ItemType Directory -Force "$HOME\.claude\skills\human-release-notes" | Out-Null
- Copy-Item SKILL.md "$HOME\.claude\skills\human-release-notes\"
- ```
- ## Usage
- Ask your AI for release notes and paste or point to the source:
- ```
- Write release notes for users from these commits:
- <git log --oneline v1.2.0..HEAD>
- ```
- ```
- Release notes from this diff: <git diff v1.2.0..HEAD>
- ```
- If the input is unclear, the skill asks up to three questions before writing.
- ## Example output
- ```
- ## New
- - You can export your reports to CSV from the Reports screen.
- ## Improved
- - Search results load faster on large accounts.
- ## Fixed
- - Dates no longer show one day off for users in UTC-3.
- ```
- ## License
- MIT. See [LICENSE](LICENSE).
- ---
- Made by [PLAF Labs](https://github.com/plaf-labs) · Software, automation and web development for SMEs and
- industrial companies · [plaf.agency](https://plaf.agency)
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.