release-core-test

Publishes cyrus-core as a prerelease to npm under the test dist-tag.

794|163|Updated Apr 19, 2025
One-click install
npx skills add https://github.com/ceedaragents/cyrus --skill release-core-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-core-test
Source: https://github.com/ceedaragents/cyrus/tree/main/.claude/skills/release-core-test
Command: npx skills add https://github.com/ceedaragents/cyrus --skill release-core-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev-testing a change that spans the Cyrus edgeworker/CLI and the hosted GUI requires the GUI to install an unreleased cyrus-core build, but publishing a real release would move the latest dist-tag and affect production installs.

Core Features & Use Cases

  • Test Dist-Tag Publishing: Publishes cyrus-core as a -test.N prerelease under the npm test dist-tag so latest stays untouched.
  • Conditional claude-runner Republish: Detects whether the workspace claude-runner dependency is unpublished or dirty and republishes it only when required.
  • Version Calculation: Computes the next -test.N prerelease version by querying existing npm versions and incrementing N.
  • Use Case: A developer iterating on cyrus-core runs this skill to publish cyrus-core@test, then points the CYHOST Vercel deployment at that prerelease without cutting a real release, changelog entry, git tag, or pull request.

Quick Start

Ask the agent to run a dev test release of cyrus-core by invoking the release-core-test skill.

Frequently Asked Questions about release-core-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish an npm prerelease without affecting the latest tag?

Publish with an explicit dist-tag such as pnpm publish --tag test. This makes the version installable via npm install package@test while leaving the latest dist-tag unchanged, so production installs are unaffected.

How do I test an unreleased cyrus-core version in the hosted Cyrus GUI?

Run the release-core-test skill to publish cyrus-core as a -test.N prerelease under the npm test dist-tag, then configure CYHOST to install cyrus-core@test. No real release, git tag, or changelog update is created.

When does claude-runner need to be republished alongside cyrus-core?

Republish claude-runner when its local version is not on npm or when its source has uncommitted changes since the last publish. Otherwise cyrus-core's rewritten workspace dependency would fail to resolve for consumers installing cyrus-core@test.

Does this skill create a git tag or GitHub release?

No. The skill intentionally skips changelog updates, git tags, GitHub releases, pull requests, and commits. The version bump in package.json is left as an uncommitted local working-tree change.

Why use --no-git-checks when publishing from a feature branch?

The --no-git-checks flag allows pnpm publish to run from a feature branch with a dirty working tree. Without it, pnpm would refuse to publish unless the tree is clean and on the expected release branch.