cp-yu/cc-switch-web/cc-switch-release

Claude Code and agent skill by cp-yu/cc-switch-web

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

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.

Install

npx vskill@latest install cp-yu/cc-switch-web/cc-switch-release

SKILL.md

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

  1. Inspect repo state first.

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

  1. Decide the operation.

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

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

  1. Run the repo helper.

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

  1. 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<version> --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

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

See the full security report

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

Popularity

Repository stars
48
Repository forks
10
7-day trend score
24

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/cp-yu/cc-switch-web/cc-switch-release/badge)](https://verified-skill.com/skills/cp-yu/cc-switch-web/cc-switch-release)

Something wrong with this skill or its page? Tell us.