Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control.
SkillScore96Maintained
Automatic
◆Doc Ops pack
Last verified 8/4/2026
What it changes
Passed 22 of 23 test cases with the skill, and 11 of 23 without it.
Without skill48%
With skill96%
Checks it passed that the model alone missed
Specifies --output-format json.
Passes --next-version v1.4.0 in the arguments.
States the P0 resolution SLA is 2 hours or less.
and 17 more in the full report
11 fixed11 passed either way1 still failing0 broke
Pass-rate lift
+48 pp
Tokens
+66%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/4/2026v122 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
We need the version calculation script to output the precise git tag commands required to apply the recommended version bump alongside the JSON output. Which flag enables this in the output?
What was checked, without and with the skill
Checked
Without skill
With skill
Includes --include-commands when running scripts/version_bumper.py.
Missed
Passed
case-08 · gemini-3.6-flash · 8/4/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
Use this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control.
Core Capabilities
Parse commit messages using Conventional Commit rules
Detect semantic bump (major, minor, patch) from commit stream
Render Keep a Changelog sections (Added, Changed, Fixed, etc.)
Generate release entries from git ranges or provided commit input
Enforce commit format with a dedicated linter script
Support CI integration via machine-readable JSON output
When to Use
Before publishing a release tag
During CI to generate release notes automatically
During PR checks to block invalid commit message formats
In monorepos where package changelogs require scoped filtering
When converting raw git history into user-facing notes