Good skill
Use when the user asks an AI coding agent to turn a git diff into concise release notes with risks, validation evidence, and reviewer-ready wording.From its SKILL.md
npx -y skills add Sparvovic/agent-skill-foundry --skill good-skillAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.
SKILL.md
1.5 KB, 277 tokens by cl100k_base, as published. Nobody here has run it
Release Note Review
Purpose
Create clear release-note drafts from a local diff without hiding risk or inventing user impact.
Use When
Use this skill when the user asks for release notes, changelog text, launch notes, or a reviewer handoff based on local code changes.
Inputs
- The current git diff.
- Existing changelog or release-note style, if present.
- Package manifests or docs that identify the product area.
Workflow
- Inspect the diff and nearby docs before writing.
- Separate user-visible changes from internal refactors.
- Flag migrations, behavior changes, removed APIs, and validation gaps.
- Draft concise release notes in the existing project voice.
- Keep uncertainty explicit when impact cannot be proven from the diff.
Outputs
- A Markdown release-note draft.
- A short risk section.
- Validation evidence and commands that were run.
Validation
Run the repo's relevant test, build, or lint command before finalizing. If no validation command is available, state that clearly.
Safety Boundaries
- Do not claim tests passed unless the command was run.
- Do not invent customer impact that is not visible in the diff.
- Do not publish or submit release notes externally without user approval.
Additional Resources
- Read references/release-note-checklist.md before preparing a public release note.
What ships with it: 1 file
257 B alongside SKILL.md