agentleFS
jamie8johnsonjamie8johnson/cqs/.claude/skills/release/SKILL.md

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

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.
  • MicrosoftSkill

    create-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

  • GrinvSkill

    changelog-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 AzureSkill

    component-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

  • GrinvSkill

    docs-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 AzureSkill

    documentation-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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

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
  1. Distinctive:

    Run BOTH fixtures against the current index:

    line 26
  2. Very specific:

    If numbers dropped: check for dead gold origins FIRST — the matcher is (origin, name), so file splits/renames since the last release kill …

    line 32
  3. Very specific:

    Read current version from Cargo.toml

    line 36
  4. Very specific:

    Update Cargo.toml version field

    line 38
  5. Very specific:

    Run cargo check to update Cargo.lock

    line 39
  6. Very specific:

    Run /docs-review. Fix anything stale before cutting the release.

    line 42
  7. Distinctive:

    Update the compare links at the bottom of the file

    line 53
  8. Very specific:

    Create PR via PowerShell with --body-file (never inline heredocs): write body to /mnt/c/Projects/cqs/pr_body.md, use it, delete it

    line 59
  9. Very specific:

    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 …

    line 78
  10. Very specific:

    Update PROJECT_CONTINUITY.md with new version

    line 81
  11. Distinctive:

    Update ROADMAP.md if phase milestones changed

    line 82
  12. Very specific:

    Always use --body-file for PR/release bodies — never inline heredocs

    line 89
  13. Very specific:

    Write body content to /mnt/c/Projects/cqs/pr_body.md, use it, then delete

    line 90

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release

Release a new version of cqs.

Arguments

  • $ARGUMENTS — version bump type: major, minor, or patch (default: patch)

Process

  1. 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 main branch
  2. 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.
  3. Version bump:
    • Read current version from Cargo.toml
    • Calculate new version based on bump type
    • Update Cargo.toml version field
    • Run cargo check to update Cargo.lock
  4. 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.md TL;DR line (R@1/R@5/R@20 + snapshot date/corpus size)
    • Cargo.toml description (crates.io one-liner quotes the same numbers)
    • GitHub repo description: gh repo view / gh repo edit --description (via PowerShell)
  5. Changelog:
    • Read CHANGELOG.md
    • Stamp the ## [Unreleased] section into ## [X.Y.Z] - YYYY-MM-DD (run date first; create the section from git log since the last tag if no Unreleased block exists)
    • Categorize: Added, Changed, Fixed, Removed
    • Update the compare links at the bottom of the file
  6. Commit and tag:
    • Create branch: release/vX.Y.Z
    • cargo fmt then 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.0 aarch64-apple-darwin E0277) 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
  7. After PR merge:
    • Sync main: git checkout main && git pull, then cqs index (watch misses bulk git ops on WSL)
    • Tag: git tag vX.Y.Z and 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-macros FIRST, wait for it to land on crates.io, then cargo publish -p cqs. Otherwise just cargo publish -p cqs.
  8. 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 push works directly from WSL (credential helper wired); PowerShell is the fallback when GCM crashes ("could not read Username")
  • All gh commands go through PowerShell (with cd C:\Projects\cqs or -R jamie8johnson/cqs)
  • Always use --body-file for PR/release bodies — never inline heredocs
  • Write body content to /mnt/c/Projects/cqs/pr_body.md, use it, then delete

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.