CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-notes

Draft release notes from merged pull requests since the last tag. Use when preparing a release.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Release notes

Find the most recent tag, list the pull requests merged since it, and group them by their conventional-commit type (features, fixes, other). Write one line per pull request in plain language, naming the user-visible change rather than the implementation.

Skip pull requests whose title starts with chore: or ci: unless they change something a user would notice.

Put the draft in RELEASE_NOTES.md at the repository root and show it to the user. Do not create the tag or publish the release.

Repository

EveryInc/compound-engineering-plugin

Path

tests/skill-eval-cell/fixtures/review-roster-skill-prose/skills/release-notes/SKILL.md

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.