Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ratel-ai/changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc.* sections into a single X.Y.Z section). Invoke before tagging a release.
Passed 16 of 18 test cases with the skill, and 7 of 18 without it.
and 11 more in the full report
11 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which specific path in the repository holds the release history for the `telemetry-core` Rust crate?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies src/telemetry/core/CHANGELOG.md as the changelog location for telemetry-core | Missed | Passed |
The instructions your model reads when the skill loads.
Updates a release unit's CHANGELOG.md in preparation for tagging it. Ratel releases
per unit (ADR-0008): each unit ships on its own tag (<prefix>-v*) at its own version.
For workflow-wired units, .github/workflows/release.yml rejects a tag whose unit CHANGELOG
doesn't contain the version being released. vercel-ai-sdk is temporarily published
manually via scripts/publish-rc.sh; still run this skill before its tag even though the
workflow gate does not cover it yet.
Run it once per unit you're releasing.
The units and their manifests/CHANGELOGs live in one registry —
scripts/release-units.mjs — which every release tool reads. Run node scripts/release-units.mjs --list
for the authoritative set; the current eight units are:
| Unit | Registry | CHANGELOG path |
|---|---|---|
core | ratel-ai-core (crates.io) | src/core/CHANGELOG.md |
sdk-ts | @ratel-ai/sdk (npm) | src/sdk/ts/CHANGELOG.md |
sdk-py | ratel-ai (PyPI) | src/sdk/python/CHANGELOG.md |
telemetry-core | ratel-ai-telemetry (crates.io) | src/telemetry/core/CHANGELOG.md |
telemetry-ts | @ratel-ai/telemetry (npm) | src/telemetry/ts/CHANGELOG.md |
telemetry-py | ratel-ai-telemetry (PyPI) | src/telemetry/python/CHANGELOG.md |
vercel-ai-sdk | @ratel-ai/vercel-ai-sdk (npm) | src/adapters/ts-vercel-ai-sdk/CHANGELOG.md |
mastra | @ratel-ai/mastra (npm) | src/adapters/ts-mastra/CHANGELOG.md |
@ratel-ai/mcp-server lives in ratel-ai/ratel-mcp and maintains its own CHANGELOG there.
If the user hasn't named the unit, run node scripts/releasable.mjs — it lists which
units have commits since their last release tag. Pick the unit $UNIT being released.
Read its canonical version:
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.