Repository navigation
v2.22.0
What's new
Features
A new project-scoped skill at .agents/skills/release-notes-narrative/ that turns sparse semantic-release output into useful changelog narrative. The skill is loaded on demand by any agent to patch a published GitHub release body via gh release edit --notes-file, defending against two known release-notes-generator failure modes already observed on this repo: bare bucket bullets (semantic-release ingests only commit subject lines, never commit bodies or PR descriptions) and spurious closes [URL-fragment] autolinks (the generator misparses path#fragment substrings in commit bodies as Closes #N footers).
The skill ships as a 13-step procedure with a hardcoded bucket map mirrored from .releaserc.yaml, a calibrated thin-commit-body threshold for triggering PR-body enrichment, and a 4-condition AST-based autolink-strip allowlist with documented positive and negative examples. Three-layer defense for the live gh release edit step (pre-edit snapshot, preflight check, post-edit rollback) keeps blast radius bounded. Structural idempotence — same buckets, same Compare link, same referenced PRs across reruns — is the explicit guarantee; LLM-generated narrative prose is allowed to vary by run (#429).
This release is itself the first dogfood: the skill was applied to v2.20.5, v2.20.6, and v2.21.0 retroactively as acceptance evidence before merge, and the v2.22.0 release notes you're reading now are the skill's output.