Release Notes Agent
Release Notes Agent
ChatGPTClaudeGitHub🔌 MCP-ready
Health
80/100
▲ 0
📋 0 copies
Trigger Phrase
Use the Release Notes Agent skill
Prompt
255 words# SKILL: Release Notes Agent
## Purpose
Turn technical changes into release notes that users and internal teams can understand.
## When to Use
Use this when the user needs to: Turn technical changes into release notes that users and internal teams can understand. It is designed for repeatable agent or automation work, not one-off fluffy prompting.
## Inputs Required
- Merged PRs or commits
- Release version
- Audience
- Known breaking changes
- Support notes
## Workflow
1. Group changes by user impact
2. Separate new, improved, fixed, and breaking changes
3. Avoid exposing sensitive implementation details
4. Add migration or support notes
5. Draft internal and external variants
## Output Format
Release notes with public summary, internal notes, and support talking points.
## Quality Rules
- Ground every claim in supplied inputs or clearly mark it as an assumption.
- Prefer specific fields, examples, and decision points over generic advice.
- Include a test command and pass criteria so the skill can be evaluated.
- Keep the output usable by a human first and automation-ready second.
## Guardrails
- Do not send emails, publish posts, contact leads, change calendars, spend money, delete data, or alter production systems without explicit human approval.
- Do not invent facts, private details, legal claims, prices, or external data.
- For web or profile research, use current sources and separate evidence from inference.
- For connected tools, use the minimum permission needed and log the action taken.
## Test Command
Run this skill on a simple example for Release Notes Agent and return the expected output structure plus any missing inputs.
## Purpose
Turn technical changes into release notes that users and internal teams can understand.
## When to Use
Use this when the user needs to: Turn technical changes into release notes that users and internal teams can understand. It is designed for repeatable agent or automation work, not one-off fluffy prompting.
## Inputs Required
- Merged PRs or commits
- Release version
- Audience
- Known breaking changes
- Support notes
## Workflow
1. Group changes by user impact
2. Separate new, improved, fixed, and breaking changes
3. Avoid exposing sensitive implementation details
4. Add migration or support notes
5. Draft internal and external variants
## Output Format
Release notes with public summary, internal notes, and support talking points.
## Quality Rules
- Ground every claim in supplied inputs or clearly mark it as an assumption.
- Prefer specific fields, examples, and decision points over generic advice.
- Include a test command and pass criteria so the skill can be evaluated.
- Keep the output usable by a human first and automation-ready second.
## Guardrails
- Do not send emails, publish posts, contact leads, change calendars, spend money, delete data, or alter production systems without explicit human approval.
- Do not invent facts, private details, legal claims, prices, or external data.
- For web or profile research, use current sources and separate evidence from inference.
- For connected tools, use the minimum permission needed and log the action taken.
## Test Command
Run this skill on a simple example for Release Notes Agent and return the expected output structure plus any missing inputs.
Before & After
❌ Without this prompt
Make me an automation for release notes agent.
✅ With this prompt
Use the Release Notes Agent skill. Inputs: goal, systems, data fields, approval owner, and definition of done. Return the workflow, tests, guardrails, and approval checkpoint.
Install Instructions
Copy the body into Prompt Hub as a skill. For Agent Skills, save as SKILL.md or paste into the target agent/project. For n8n/Make/Voiceflow, use this as the build blueprint before importing any third-party JSON.
Test It
Test command:
Run Release Notes Agent with a tiny dummy case and verify it returns the declared output format, missing-input warnings, guardrails, and pass criteria.
Expected output:
Release notes with public summary, internal notes, and support talking points.
Pass criteria:
- Passes when the output is specific, complete, safe, testable, approval-aware where needed, and immediately usable with light editing.
⚠️ Guardrails
- Human approval is required before external sends, publishing, destructive changes, spending money, calendar booking, CRM updates that change customer status, or production system changes. Use least-privilege tool access.
📁 Context File Tip
Source context: Sabrina Ramonov describes agents.sabrina.dev as a free library of AI agents and automations, including n8n and Make templates. Related source: https://agentskills.io/home. Agent-skill structure context: https://agentskills.io/home. Security context: https://arxiv.org/abs/2510.26328.
⚡ Automation
ChatGPT|Claude|GitHub
🔌 MCP-compatible