release-core-test
Skill888 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
- cyrusagents/cyrusword for word, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cyrusagents/cyrus★ 902100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- cyrus-setup-claude-authSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-gitlabSkill
- cyrus-setup-launchSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- cyrus-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
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
- Very specific: line 14
Update CHANGELOG.md or CHANGELOG.internal.md
- Distinctive: line 15
Create a git tag
- Distinctive: line 16
Create a GitHub release
- Very specific: line 19
Commit the version bump (the bumped package.json is left as a local working-tree change)
- Distinctive: line 43
Run both of these deterministic checks:
- Very specific: line 73
Read the current version from packages/core/package.json (e.g.
- Very specific: line 77
Use this one-liner to find existing -test.N versions for the bumped patch and pick the next N:
- Very specific: line 89
Write the chosen version (e.g.
- Distinctive: line 114
After publishing, print both forms so the developer can copy/paste:
- Very specific: line 125
If claude-runner was also republished in step 3, include its version too.
- Very specific: line 129
Always use --no-git-checks so you can publish from a feature branch with a dirty working tree.
- Very specific: line 130
Always use --tag test so the latest dist-tag is preserved for real releases.
- Very specific: line 132
Run pnpm install after publishing claude-runner (if applicable) so the lockfile reflects the new published version before cyrus-core is …
≈ “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
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.mdorCHANGELOG.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.jsonis 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 install2. Build all packages from repo root
pnpm buildBuilding 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-runnerOtherwise, skip this step entirely.
4. Bump cyrus-core to the next -test.N prerelease version
Algorithm:
- Read the current version from
packages/core/package.json(e.g.0.1.22). - Bump the patch (e.g.
0.1.23). - Append
-test.N, starting atN = 0and incrementing while<bumped>-test.Nalready 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@testwill install this version.- The
latestdist-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-tagsConfirm 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-checksso you can publish from a feature branch with a dirty working tree. - Always use
--tag testso thelatestdist-tag is preserved for real releases. - Prerelease versions (anything with a
-suffix like-test.0) are never auto-installed bynpm install cyrus-corewithout an explicit tag or version spec, so this is safe to run repeatedly. - Run
pnpm installafter publishingclaude-runner(if applicable) so the lockfile reflects the new published version beforecyrus-coreis built/published. pnpm install+pnpm buildfrom 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
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.

