Release notes changelog

Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.

Install

npx -y skills add jukrap/ai-agent-playbook --skill release-notes-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

Copied from the file, not written here

Use when preparing release notes, changelogs, migration notes, rollback notes, or known issues.

1.2 KB, as published. Nobody here has run it

Translate shipped or planned changes into reader-facing release artifacts without copying commit history.

Identify the reader: user, support, operator, developer, maintainer, stakeholder, or migration owner.
Group changes by user impact, operational impact, migration impact, known issue, and rollback or support note.
Separate verified behavior from implementation detail, commit titles, worklog notes, and generated summaries.
Include risk, caveat, compatibility, migration, rollback, and monitoring notes when relevant.
Cite only reviewed evidence and actual verification results; do not invent tests or release status.
Keep private paths, credentials, internal URLs, branch names, PR numbers, and noisy reference names out of the artifact.

Read references/release-note-audience-checks.md when choosing release artifact structure and reader detail.

Read references/changelog-risk-and-rollback.md when documenting risk, known issues, migrations, rollback, or verification evidence.