release-notes
Authoritative protocol for authoring release notes as an EPIC with mining-driven iterations — scope derivation (the tracker lags shipped reality), heavy per-arc Memory-Core mining, per-claim V-B-A, the precedent-SET quality bar — majors AND minors, v13.0.0 + v12.1.0 + v11.22-24 (hero chapters, named case studies with real timelines, War Stories, honest bounds, never downplay a release), and the publish.mjs flat-root staging lifecycle. Triggers: a release window opens, release notes are requested/authored/iterated, or cut-prep begins (staging file, atomic-hash line, orphan-guard interplay).
75
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Release Notes Skill
If you are authoring, iterating, reviewing, or cut-preparing release notes, you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/release-notes/references/release-notes-workflow.md before writing, judging, or moving any notes content.
- Repository
- neomjs/neo
- Commit
c1ce853
- 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.