agentleFS
cyrusagentscyrusagents/cyrus/.claude/skills/release-core-test/SKILL.md

release-core-test

Skill902 starsChanged 53 days agoApache-2.0View on GitHub

Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased `cyrus-core` from this repo. Publishes `cyrus-core` (and `claude-runner` if needed) as a `-test.N` prerelease under the npm `test` dist-tag so CYHOST can install it via `cyrus-core@test` without affecting the `latest` dist-tag or shipping a real release.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 4 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Very specific:

    Update CHANGELOG.md or CHANGELOG.internal.md

    line 14
  2. Distinctive:

    Create a git tag

    line 15
  3. Distinctive:

    Create a GitHub release

    line 16
  4. Very specific:

    Commit the version bump (the bumped package.json is left as a local working-tree change)

    line 19
  5. Distinctive:

    Run both of these deterministic checks:

    line 43
  6. Very specific:

    Read the current version from packages/core/package.json (e.g.

    line 73
  7. Very specific:

    Use this one-liner to find existing -test.N versions for the bumped patch and pick the next N:

    line 77
  8. Very specific:

    Write the chosen version (e.g.

    line 89
  9. Distinctive:

    After publishing, print both forms so the developer can copy/paste:

    line 114
  10. Very specific:

    If claude-runner was also republished in step 3, include its version too.

    line 125
  11. Very specific:

    Always use --no-git-checks so you can publish from a feature branch with a dirty working tree.

    line 129
  12. Very specific:

    Always use --tag test so the latest dist-tag is preserved for real releases.

    line 130
  13. Very specific:

    Run pnpm install after publishing claude-runner (if applicable) so the lockfile reflects the new published version before cyrus-core is …

    line 132

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

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

Release Core (Test)

Publish ONLY the cyrus-core package (and claude-runner if needed) as a dev/test prerelease to npm under the test dist-tag. This is a developer convenience for iterating on cyrus-core without going through the full release flow.

What this skill does NOT do

This skill is intentionally minimal. It does NOT:

  • Update CHANGELOG.md or CHANGELOG.internal.md
  • Create a git tag
  • Create a GitHub release
  • Move any Linear issues
  • Open a pull request
  • Commit the version bump (the bumped package.json is left as a local working-tree change)

It also does NOT publish any other workspace package (no edge-worker, no cyrus CLI, no linear-event-transport, etc.). The only exception is claude-runner, which is republished if and only if its workspace:* reference would otherwise resolve to an unpublished version (see step 3 below).

Workflow

1. Install dependencies from repo root

pnpm install

2. Build all packages from repo root

pnpm build

Building all packages ensures workspace:* dependencies are resolved before publishing.

3. Determine whether claude-runner needs republishing

cyrus-core depends on claude-runner via workspace:*. When cyrus-core is published, that workspace:* is rewritten to the version currently in packages/claude-runner/package.json. If that version isn't actually on npm yet (because claude-runner has local changes since its last publish), consumers installing cyrus-core@test will fail to resolve the dependency.

Run both of these deterministic checks:

# (a) Is the local claude-runner version already on npm?
LOCAL_CR=$(node -p "require('./packages/claude-runner/package.json').version")
npm view "cyrus-claude-runner@${LOCAL_CR}" version 2>/dev/null

# (b) Does claude-runner have uncommitted/unpushed source changes since its last publish?
git diff --quiet HEAD -- packages/claude-runner/src packages/claude-runner/package.json && echo "clean" || echo "dirty"

Republish claude-runner if either: (a) returns nothing (local version is not on npm), or (b) prints dirty. If both pass cleanly, skip this step. If you're unsure, ask the user.

To republish:

# Determine the next -test.N for claude-runner (same algorithm as cyrus-core below)
# Bump packages/claude-runner/package.json to e.g. 0.0.X-test.N
cd packages/claude-runner
pnpm publish --access public --no-git-checks --tag test
cd ../..
pnpm install   # refresh lockfile so cyrus-core picks up the new claude-runner

Otherwise, skip this step entirely.

4. Bump cyrus-core to the next -test.N prerelease version

Algorithm:

  1. Read the current version from packages/core/package.json (e.g. 0.1.22).
  2. Bump the patch (e.g. 0.1.23).
  3. Append -test.N, starting at N = 0 and incrementing while <bumped>-test.N already exists on npm (including aborted/stale prior attempts).

Use this one-liner to find existing -test.N versions for the bumped patch and pick the next N:

BUMPED=0.1.23   # the patch-bumped base, no suffix
npm view cyrus-core versions --json \
  | jq -r '.[]' \
  | grep -E "^${BUMPED}-test\.[0-9]+$" \
  | awk -F'test.' '{print $2}' \
  | sort -n | tail -1
# If empty, use N=0. Otherwise use (max + 1).

Write the chosen version (e.g. 0.1.23-test.0) back into packages/core/package.json. Do NOT commit this change — leave it as a local working-tree edit so the developer can decide whether to keep it.

5. Publish cyrus-core with the test dist-tag

cd packages/core
pnpm publish --access public --no-git-checks --tag test
cd ../..

Using --tag test means:

  • npm install cyrus-core@test will install this version.
  • The latest dist-tag is not moved, so production installs (npm install cyrus-core) are unaffected.

6. Verify the dist-tags landed correctly

npm view cyrus-core dist-tags

Confirm that latest is unchanged from before the publish and test now points to the version you just published. If latest moved, something is wrong — stop and investigate before telling anyone to install it.

7. Print install instructions

After publishing, print both forms so the developer can copy/paste:

Published cyrus-core@<version> under dist-tag `test`.

Install with:
  npm install cyrus-core@test
or pinned:
  npm install cyrus-core@<version>

If claude-runner was also republished in step 3, include its version too.

Key Notes

  • Always use --no-git-checks so you can publish from a feature branch with a dirty working tree.
  • Always use --tag test so the latest dist-tag is preserved for real releases.
  • Prerelease versions (anything with a - suffix like -test.0) are never auto-installed by npm install cyrus-core without an explicit tag or version spec, so this is safe to run repeatedly.
  • Run pnpm install after publishing claude-runner (if applicable) so the lockfile reflects the new published version before cyrus-core is built/published.
  • pnpm install + pnpm build from root takes ~3 minutes combined on a clean tree — plan command timeouts accordingly.

Examples

  • "release core test" - Run a dev release of cyrus-core
  • "/release-core-test" - Invoke this skill

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.