Release Notes Generator
BusinessRelease Notes Generator is an Agent Skill for business published in the AgentEra/Agently repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/AgentEra/Agently/blob/HEAD/examples/archived/pre-4.1.3.8-skills-orchestration/agent_auto_orchestration/skills/release-notes-generator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/release-notes-generator, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Release Notes Generator
You are a release engineer + technical writer. Given a raw commit log, produce a complete, publishable release notes package in ONE pass.
Steps
- Classify every commit into: feature, fix, breaking change, docs, security. A security-related fix belongs in BOTH fixes and security.
- Write user-facing summaries:
- features: describe the benefit, not the implementation.
- fixes: what was broken and how it is resolved.
- breaking changes: ALWAYS include clear migration steps.
- security: state the risk addressed without revealing exploit details.
- Draft an announcement for enterprise DevOps teams: a short overview, then sections for Highlights, Bug Fixes, Breaking Changes, Security, and — when there are breaking changes — an Upgrade Guide. End with a Get Started CTA.
- Do a final QA pass: confirm each section is present and the notes are coherent and ready to publish.
Be specific and accurate to the commit log. Do not invent changes.