Release notes review
Governed, replay-tested agent skills for Codex-style maintainer workflows.
npx -y skills add 2702207741-dev/agent-skills-pipeline --skill release-notes-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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.
What its author says it does
Copied from the file, not written here
Review release-note behavior, regression evidence, and package readiness for this repository before a release.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.0 KB, as published. Nobody here has run it
Release Notes Review
Use issue evidence and local tests to decide whether a release-notes change can pass the repository release gate.
When to Use
- Release-note parsing or formatting changes.
- A release gate needs regression and rollback evidence.
- A maintainer reviews a patch tied to a release-note issue.
Workflow
- Read the issue and acceptance criteria.
- Reproduce the old behavior without network access.
- Review the patch for compatibility and unsafe side effects.
- Run the full local unit test suite.
- Approve only when the regression is fixed and the package gate passes.
Verification Checklist
- The issue is reproducible before the patch.
- The acceptance criteria map to tests.
- The fixed suite passes.
- No network, secret, or destructive command is introduced.
- The release artifact, manifest, and checksum verify.