cc-switch-web: Skill for Claude Code

Archive a completed change in the Xirang change workflow.

Xirang Philosophy

1. Xirang is a structured representation of human intent that an Agent can compile.
2. One Xirang Semantic Model is persisted as a single whole in the four partitions metamodel/, elements/, relationships/, and views/; a Semantic Delta uses the same four partitions and adds operation.
3. A change reconciles a Semantic Delta toward the target steady state. proposal.md, design.md, and tasks.md are compilation scaffolding, not competing sources of truth.
4. The Xirang Semantic Model is complete only when an Agent need not guess decisions that affect element hierarchy, contracts, or relationships.
5. The Agent acts like a compiler and faithfully translates authorized human intent. Existing code is current implementation evidence and MUST NOT silently override the Xirang Semantic Model.

For workflow-managed writes, read the resolved file definition before its instruction and template, and MUST NOT copy definitions, config projections, or reasoning into artifacts.

Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Before archiving, run xirang config project --json and consume git policy from its normalized project config: git.commitMessage.archive, git.commitMessage.merge, git.merge.strategy, and git.branch.deleteAfterArchive; do not parse raw YAML inside the skill.

Steps

1. Select change If no clear change name is provided, run xirang list --json, show active changes with schema, and ask. Do not guess. Read .apply-isolation.json before running the archive CLI and retain its validated method, branchName, originalBranch, worktreePath, and sourceRoot values because the CLI moves the active change directory.

2. Unified Full Verify Gate Run xirang verify status "<change-name>" --json. Treat freshness.status as the sole signal for rerunning full verify: only MISSING or STALE enters Step 2.5. MUST NOT infer staleness from checks, details, or information. A FRESH result after seal MUST reuse Phase 1 even when Git HEAD information differs. For a fresh result, resolve incompatible optimization states separately: complete PENDING_VERIFICATION through the appropriate xirang verify phase2 call, and hard-stop ABORTED_UNSAFE for manual recovery.

2.5. Execute Full Verify

When the verify result is missing or stale, execute the same verify contract as /xirang:verify using the subagent-orchestrated skeleton:

• Determine changeName, absolute changeDir, and absolute projectRoot
• Delegate to clean-context generated xirang-reviewer subagent with context: "fresh"; pass only changeName, changeDir, projectRoot, and the explicit evidence bundle required for canonical Phase 1
• Validate the reviewer payload, apply only deterministic tasks.md write-back in the main workspace, and persist the canonical Phase 1 payload
• Execute the verify workflow end-to-end; when Phase 2 is eligible, delegate to clean-context generated xirang-optimizer subagent with context: "fresh", pass only changeName, changeDir, and projectRoot, validate its finding reconciliation envelope, and let the master implement only the selected finding with TDD
• In P1_SPECULATIVE_FENCE, delegate to clean-context generated xirang-reviewer subagent again with context: "fresh" to verify specs and the selected finding's preservationConstraints, not optimization value
• The top-level archive flow MUST NOT inline a current-agent review skeleton or silently downgrade to reread mode Continue through Phase 2 when eligible; SKIPPED is valid only for config/user skip. Persist fresh verify before archiving.

1. Check artifact completion status Run xirang status --change "<name>" --json. Warn and confirm before proceeding if any artifact is not done.