CtrlK
BlogDocsLog inGet started
Tessl Logo

Release Notes Generator

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.

SKILL.md
Quality
Evals
Security

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

  1. Classify every commit into: feature, fix, breaking change, docs, security. A security-related fix belongs in BOTH fixes and security.
  2. 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.
  3. 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.
  4. 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.

Repository
AgentEra/Agently
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.