release
Skill18 starsChanged 5 months agoMITView on GitHub
Release a new version of cqs. Bumps version, updates changelog, runs the recall gate, publishes to crates.io, creates GitHub release.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
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 repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- archeoSkill
- auditSkill
- before-editSkill
- boundary-probeSkill
- check-my-workSkill
- cqs-batchSkill
- cqs-bootstrapSkill
- cqs-planSkill
- cqsSkill
- cqs-verifySkill
- docs-reviewSkill
- groom-notesSkill
- idleSkill
- investigateSkill
- landSkill
- migrateSkill
- prSkill
- recall-gateSkill
- reindexSkill
- troubleshootSkill
- update-tearsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 3 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Run BOTH fixtures against the current index:
- Very specific: line 32
If numbers dropped: check for dead gold origins FIRST — the matcher is (origin, name), so file splits/renames since the last release kill …
- Very specific: line 36
Read current version from Cargo.toml
- Very specific: line 38
Update Cargo.toml version field
- Very specific: line 39
Run cargo check to update Cargo.lock
- Very specific: line 42
Run /docs-review. Fix anything stale before cutting the release.
- Distinctive: line 53
Update the compare links at the bottom of the file
- Very specific: line 59
Create PR via PowerShell with --body-file (never inline heredocs): write body to /mnt/c/Projects/cqs/pr_body.md, use it, delete it
- Very specific: line 78
Publish order: if cqs-macros/ changed since the last release, cargo publish -p cqs-macros FIRST, wait for it to land on crates.io, then …
- Very specific: line 81
Update PROJECT_CONTINUITY.md with new version
- Distinctive: line 82
Update ROADMAP.md if phase milestones changed
- Very specific: line 89
Always use --body-file for PR/release bodies — never inline heredocs
- Very specific: line 90
Write body content to /mnt/c/Projects/cqs/pr_body.md, use it, then delete
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release
Release a new version of cqs.
Arguments
$ARGUMENTS— version bump type:major,minor, orpatch(default:patch)
Process
- Pre-flight checks:
git status— must be clean (no uncommitted changes)gh pr list --state open(via PowerShell) — review any open PRs. Merge or close before releasing.cargo test --features cuda-index— all tests must pass (full suite is correct here; this is the one place it runs deliberately)cargo clippy --all-targets --features cuda-index -- -D warnings— no warnings (CI runs--all-targets)- Confirm on
mainbranch
- Recall gate (REQUIRED before tagging):
- Run BOTH fixtures against the current index:
cqs eval evals/queries/v3_test.v2.json --json cqs eval evals/queries/v3_dev.v2.json --json - Compare R@1/R@5/R@20 against the previous release's snapshot (README TL;DR line / RESULTS log).
- If numbers dropped: check for dead gold origins FIRST — the matcher is
(origin, name), so file splits/renames since the last release kill gold origins and cap R@K, masquerading as a recall regression. Line-number drift alone is harmless. - The definitive regression test is a same-corpus binary A/B: run the previous release binary and the new one against the SAME index and diff the reports. Only a regression confirmed by the A/B blocks the release.
- Run BOTH fixtures against the current index:
- Version bump:
- Read current version from
Cargo.toml - Calculate new version based on bump type
- Update
Cargo.tomlversion field - Run
cargo checkto updateCargo.lock
- Read current version from
Docs review: Run
/docs-review. Fix anything stale before cutting the release.Eval-number sync — if the recall-gate numbers changed, update every surface that quotes them:
README.mdTL;DR line (R@1/R@5/R@20 + snapshot date/corpus size)Cargo.tomldescription(crates.io one-liner quotes the same numbers)- GitHub repo description:
gh repo view/gh repo edit --description(via PowerShell)
- Changelog:
- Read
CHANGELOG.md - Stamp the
## [Unreleased]section into## [X.Y.Z] - YYYY-MM-DD(rundatefirst; create the section fromgit logsince the last tag if no Unreleased block exists) - Categorize: Added, Changed, Fixed, Removed
- Update the compare links at the bottom of the file
- Read
- Commit and tag:
- Create branch:
release/vX.Y.Z cargo fmtthen commit:chore: Release vX.Y.Z- Push from WSL:
git push -u origin release/vX.Y.Z(PowerShell only as fallback if GCM crashes) - Create PR via PowerShell with
--body-file(never inline heredocs): write body to/mnt/c/Projects/cqs/pr_body.md, use it, delete it - Wait for CI — pin the run ID (do NOT use
gh pr checks --watch; it latches onto the previous commit's completed run):sleep 45 powershell.exe -Command 'cd C:\Projects\cqs; gh run list --branch release/vX.Y.Z --workflow CI --limit 1' powershell.exe -Command 'cd C:\Projects\cqs; gh run watch RUN_ID --exit-status' - Pre-tag cross-build dry-run (REQUIRED — catches macOS/Windows breaks the Linux-only PR CI can't see). The
v*tag is the only thing that builds all three release targets, so a platform-specific break (e.g. the v1.46.0aarch64-apple-darwinE0277) is otherwise invisible until you've already tagged and published the crate. Trigger release.yml on the release branch as a build-only dry-run (it skips the "Create GitHub Release" job, which is gated on a tag ref) and confirm all three Build jobs pass BEFORE tagging:powershell.exe -Command 'cd C:\Projects\cqs; gh workflow run release.yml --ref release/vX.Y.Z' sleep 45 powershell.exe -Command 'cd C:\Projects\cqs; gh run list --workflow release.yml --limit 1 --json databaseId,headBranch' # poll `gh run view <id> --json status,conclusion,jobs`; every Build job must be green before you tag
- Create branch:
- After PR merge:
- Sync main:
git checkout main && git pull, thencqs index(watch misses bulk git ops on WSL) - Tag:
git tag vX.Y.Zand push it:git push origin vX.Y.Z - GitHub Release with pre-built binaries is created automatically by
.github/workflows/release.yml - Publish order: if
cqs-macros/changed since the last release,cargo publish -p cqs-macrosFIRST, wait for it to land on crates.io, thencargo publish -p cqs. Otherwise justcargo publish -p cqs.
- Sync main:
- Post-release:
- Update PROJECT_CONTINUITY.md with new version
- Update ROADMAP.md if phase milestones changed
- Rebuild and install the binary so the daemon serves the release:
cargo build --release --features cuda-index && systemctl --user stop cqs-watch && cp ~/.cargo-target/cqs/release/cqs ~/.cargo/bin/cqs && systemctl --user start cqs-watch
WSL notes
git pushworks directly from WSL (credential helper wired); PowerShell is the fallback when GCM crashes ("could not read Username")- All
ghcommands go through PowerShell (withcd C:\Projects\cqsor-R jamie8johnson/cqs) - Always use
--body-filefor PR/release bodies — never inline heredocs - Write body content to
/mnt/c/Projects/cqs/pr_body.md, use it, then delete
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.

