source-command-release
Skill136 starsChanged 3 months agoMITView on GitHub
Review and merge the release-plz release PR with explicit user confirmation
1 other project uses a version of this.
Adopted by
Most recently taken up by
- bhauman/clojure-mcptheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- bhauman/clojure-mcp★ 782same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- nxv-designSkill
- nxvSkill
- nxv-designSkill
- nxvSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when the user asks to run the migrated source command release.
- Very specific: line 30
If none exists, check whether main has unreleased conventional commits since the last tag (git log $(git describe --tags …
- Very specific: line 32
If there are releasable commits but no PR, check the latest Release-plz workflow run for errors (gh run list --workflow release-plz.yml).
- Very specific: line 38
Verify the version follows the project convention: feat: commits bump the 0.x minor (features_always_increment_minor = true), fixes bump …
- Distinctive: line 40
If the version or changelog is wrong, edit the release PR directly (it is a normal editable PR) — release-plz preserves manual edits unless …
- Very specific: line 46
All CI checks on the release PR must be green.
- Distinctive: line 64
Verify the GitHub release has all four binaries + SHA256SUMS.txt, crates.io has the new version, and ghcr.io has the version tag.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
source-command-release
Use this skill when the user asks to run the migrated source command release.
Command Template
Release
Releases are driven by release-plz (release-plz.toml +
.github/workflows/release-plz.yml). On every push to main it maintains a
chore: release vX.Y.Z PR with the version bump and CHANGELOG update derived
from conventional commits. Merging that PR ships the release — release-plz
pushes the vX.Y.Z tag, which triggers release.yml (static binaries, GitHub
release, crates.io, Docker) and flakehub-publish-tagged.yml.
This command walks that flow safely. Never merge the release PR without explicit user confirmation — it is an outward-facing, hard-to-reverse action.
Phase 1: Locate the release PR
gh pr list --repo utensils/nxv --search "chore: release in:title" --state openIf none exists, check whether main has unreleased conventional commits since
the last tag (git log $(git describe --tags --abbrev=0)..origin/main --oneline).
If there are releasable commits but no PR, check the latest Release-plz
workflow run for errors (gh run list --workflow release-plz.yml).
Phase 2: Review what will ship
- Show the PR's version bump (Cargo.toml diff) and CHANGELOG addition.
- Verify the version follows the project convention:
feat:commits bump the 0.x minor (features_always_increment_minor = true), fixes bump patch. - If the version or changelog is wrong, edit the release PR directly (it is a normal editable PR) — release-plz preserves manual edits unless new commits land on main.
Phase 3: Pre-flight
- All CI checks on the release PR must be green. If checks show "Expected /
Waiting", the App token is misconfigured — see
release-plz.ymlcomments. - Confirm no other PR is about to land that should be in this release.
Phase 4: Confirm and merge
Present a summary (version, commit list, changelog) and require the user to confirm with the explicit version number (AskUserQuestion). Then:
gh pr merge <PR> --repo utensils/nxv --squashPhase 5: Monitor
- The
Release-plzworkflow on main pushes the tag. - The
Releaseworkflow builds binaries and publishes — monitor withgh run list --workflow release.yml/gh run watch. - Verify the GitHub release has all four binaries + SHA256SUMS.txt, crates.io has the new version, and ghcr.io has the version tag.
Manual escape hatches
- Tagging failed after the release PR merged: re-run the
Release-plzworkflow on main (it is idempotent — existing tags are the gate). - The old fully-manual flow (bump Cargo.toml, edit CHANGELOG, tag by hand)
still works in emergencies but must match release-plz's expectations
(tag
vX.Y.Z, CHANGELOG section## [X.Y.Z] - YYYY-MM-DD).
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.

