create-cli-release-commit
Skill301 starsChanged 11 days agoApache-2.0View on GitHub
Create a release commit for a CLI version bump. Reads the version change in install.sh (DEFAULT_VERSION for amika or DEFAULT_AMIKALOG_VERSION for amikalog), generates a changelog from the git log between the old and new <symbol>@v* tags, and creates a commit.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- js/AGENTS.mdAGENTS.md
- sandbox-image/AGENTS.mdAGENTS.md
- amika-annotationsSkill
- amika-cliSkill
- create-sdk-release-commitSkill
- distill-sessionSkill
- make-stacked-prsSkill
- naive-reader-reviewSkill
- new-specSkill
- release-commit-sandbox-imageSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create a release commit based on a version change in install.sh.
- Distinctive: line 14
Run git diff install.sh (include both staged and unstaged changes).
- Very specific: line 25
If neither DEFAULT_VERSION nor DEFAULT_AMIKALOG_VERSION changed in the diff, error out: "No version change found in install.sh".
- Very specific: line 26
If both changed, error out: "Both DEFAULT_VERSION and DEFAULT_AMIKALOG_VERSION changed.
- Very specific: line 32
Verify both tags exist locally using git rev-parse --verify <tag>.
- Very specific: line 36
Run git log --oneline ${SYMBOL}@v${OLD_VERSION}..${SYMBOL}@v${NEW_VERSION} to get the commit log between the two tags.
- Very specific: line 40
Prefer the PR-style commit messages (the ones ending with (#NNN)) as they are the squash-merged versions.
- Distinctive: line 59
Only after the user approves the commit message:
- Very specific: line 62
Create the commit with the approved message, adding structured release trailers via --trailer:
- Very specific: line 75
Do NOT include a Co-Authored-By line in the commit message.
- Very specific: line 83
If a pull request is opened for this release (now or later), its title must start with the same [release ${SYMBOL}] prefix, e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create CLI Release Commit
Create a release commit based on a version change in install.sh. This skill detects which component is being released, extracts the old and new versions, generates a changelog from git history between the corresponding tags, and creates a well-formatted commit.
Procedure
Step 1: Detect the component and extract old and new versions
- Run
git diff install.sh(include both staged and unstaged changes). - Determine which version variable changed and set
SYMBOLandVARaccordingly:- A change to
DEFAULT_VERSION→SYMBOL=amika,VAR=DEFAULT_VERSION. - A change to
DEFAULT_AMIKALOG_VERSION→SYMBOL=amikalog,VAR=DEFAULT_AMIKALOG_VERSION. - Match
VARexactly (DEFAULT_VERSIONmust not matchDEFAULT_AMIKALOG_VERSION).
- A change to
- Parse the diff to find the old and new values for
VAR. Look for lines like:-DEFAULT_VERSION="0.5.3" +DEFAULT_VERSION="0.6.0" - Error handling:
- If neither
DEFAULT_VERSIONnorDEFAULT_AMIKALOG_VERSIONchanged in the diff, error out: "No version change found in install.sh". - If both changed, error out: "Both DEFAULT_VERSION and DEFAULT_AMIKALOG_VERSION changed; release one component at a time".
- If neither
- Record
OLD_VERSION(the removed value) andNEW_VERSION(the added value).
Step 2: Validate tags
- Construct the tag names:
${SYMBOL}@v${OLD_VERSION}and${SYMBOL}@v${NEW_VERSION}. - Verify both tags exist locally using
git rev-parse --verify <tag>. If a tag is missing, error out and tell the user which tag is missing.
Step 3: Generate changelog
- Run
git log --oneline ${SYMBOL}@v${OLD_VERSION}..${SYMBOL}@v${NEW_VERSION}to get the commit log between the two tags. - Filter out merge commits and release-tooling commits (e.g., commits that only bump version numbers). Keep substantive changes.
- Group the commits into categories if natural groupings emerge, but do not force categorization for a small number of commits. Use your judgment.
- Format each entry as a markdown list item:
- <concise description> (<short SHA>)- Prefer the PR-style commit messages (the ones ending with
(#NNN)) as they are the squash-merged versions. If both a squash-merge commit and its constituent commits appear in the log, prefer the squash-merge commit and omit the constituents.
- Prefer the PR-style commit messages (the ones ending with
Step 4: Review commit message
- Draft the commit message using this format (the subject line starts with
[release ${SYMBOL}]):
[release ${SYMBOL}] Bump install.sh ${VAR} to ${NEW_VERSION}
Release ${SYMBOL}@v${NEW_VERSION}.
Changes since ${SYMBOL}@v${OLD_VERSION}:
<changelog entries from step 3>- Present the full draft commit message to the user using
AskUserQuestionand ask them to review it. The user may request edits — apply any changes they ask for and re-present if needed.
Step 5: Create commit
Only after the user approves the commit message:
- Stage
install.sh:git add install.sh Create the commit with the approved message, adding structured release trailers via
--trailer:git commit \ -m "[release ${SYMBOL}] Bump install.sh ${VAR} to ${NEW_VERSION}" \ -m "Release ${SYMBOL}@v${NEW_VERSION}. Changes since ${SYMBOL}@v${OLD_VERSION}: <changelog entries from step 3>" \ --trailer "Release-Component: ${SYMBOL}" \ --trailer "Release-Version: v${NEW_VERSION}"
Do NOT include a Co-Authored-By line in the commit message.
Step 6: Confirm
Display the created commit (hash + full message) so the user can verify.
Step 7: Pull request
If a pull request is opened for this release (now or later), its title must start with the same [release ${SYMBOL}] prefix, e.g. [release ${SYMBOL}] Release ${SYMBOL}@v${NEW_VERSION}. Reuse the changelog from step 3 as the PR body.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

