Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/release
Release a new version of Chorus — bump version, update CHANGELOG, commit, tag, and create GitHub release.
Passed 20 of 21 test cases with the skill, and 4 of 21 without it.
and 17 more in the full report
16 fixed4 passed either way1 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When configuring Trusted Publisher settings on npmjs.org for Chorus GitHub Actions workflows, what value should be entered in the workflow filename field?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies publish-npm.yml as the exact filename. | Missed | Passed |
| Omits directory paths like .github/workflows from the npm Trusted Publisher workflow filename setting. | Passed | Passed |
The instructions your model reads when the skill loads.
Step-by-step guide to cut a new release of Chorus.
gh CLI is authenticated (gh auth status)git status)develop branch# Fetch remote tags and branches so local refs are up to date
git fetch --tags origin
# Find the previous release tag
git tag -l 'v*' --sort=-version:refname | head -5
# List commits since previous tag on develop
git log --oneline v<PREV>..develop
# Review each commit for CHANGELOG-worthy changes
git show --stat <commit-hash>
Based on the commits identified in Step 1, draft the new CHANGELOG section and present it to the user for review. Use this structure:
## [X.Y.Z] - YYYY-MM-DD
### Added
- **Feature name**: Description of what was added.
### Changed
- **Area**: Description of what changed.
test cases passed, vs 4 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.