SKILL verified MIT Self-run

Cc Switch Release

Name: Cc Switch Release
Availability: InStock
Author: cp-yu

skill-cp-yu-cc-switch-web-cc-switch-release · by cp-yu

Manage version sync, release commits, tags, pushes, and post-release verification for the cc-switch fork. Use when the user asks to bump or align versions, cut a new release, create or push a tag, verify GitHub Actions or Releases, or troubleshoot why a build artifact did not appear in the release for this repository.

↗ Repository

— No reviews yet

0 installs

13 views

0.0% view→install

Install

$ agentstack add skill-cp-yu-cc-switch-web-cc-switch-release

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

✓ Prompt-injection patterns
✓ Secret / credential exfiltration
✓ Dangerous shell & filesystem operations
✓ Untrusted network calls
✓ Known-malicious package signatures

What it can access

✓ Network access No
✓ Filesystem access No
✓ Shell / process execution No
✓ Environment & secrets No
✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Cc Switch Release? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.

About

CC Switch Release

Use this skill for repo-specific release work in cc-switch.

Core Rules

Treat origin as the release repo: cp-yu/cc-switch-web.
Treat upstream as the source mirror. Do not use it for release verification unless the user explicitly asks.
Pass -R cp-yu/cc-switch-web to gh when checking Actions or Releases. The default gh repo may point elsewhere.
Treat official GitHub Releases as Web-only. Build Web Release runs on tag push. Desktop Release (Manual) is manual only.
Keep version fields aligned in:
package.json
src-tauri/Cargo.toml
src-tauri/tauri.conf.json
Prefer scripts/release-manager.mjs over hand-editing version files when the task is version sync or release cutting.

Standard Workflow

Inspect repo state first.

Run git status --short --branch, git log --oneline --decorate -5, and if needed read [references/release-facts.md](references/release-facts.md).

Decide the operation.

Use sync when the user only wants version fields updated. Use release when the user wants commit + tag + optional push.

Preserve user intent in the index.

Do not auto-stage unrelated files. If releasing, require the intended code changes to be staged before calling the release tool.

Run the repo helper.

Version sync only: pnpm release:sync-version -- Full release: pnpm release:cut -- --push

Verify the result.

Confirm git status is clean, HEAD/tag moved as expected, and version values match. For remote verification, use: gh -R cp-yu/cc-switch-web run list --limit 5 gh -R cp-yu/cc-switch-web release view v --json tagName,name,publishedAt,url,assets

Failure Handling

If release-manager.mjs rejects the worktree, fix staging hygiene instead of bypassing the check.
If a tag already exists remotely, do not rewrite it unless the user explicitly asks for destructive history changes.
If Actions succeeded but a release is missing, verify the run and release against cp-yu/cc-switch-web, not the upstream repo.
If the task involves changing release behavior itself, edit the workflow or helper script first, then cut a new tag.

Resources

Read [references/release-facts.md](references/release-facts.md) when you need the exact repo/remotes/workflow/version-file map.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Author: cp-yu
Source: cp-yu/cc-switch-web
License: MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

v0.1.0 Imported from the upstream source.