菜单
Walk the provider cassette refresh ritual from specs/test-plan.md §4.4. Use when the user explicitly asks to refresh cassettes for a provider, or when CI flags cassette drift. Argument is the provider name (openai, anthropic, openai-compat, ollama). REFUSES to make real API calls unless OMW_CASSETTE_REFRESH=1.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks for a debt audit, codebase health check, architecture review, quality assessment of the entire omw repo, or a "what's rotten?" survey. Whole-repo scope, not diff-scoped (use /review for diffs, /simplify for tactical cleanup). Optional argument is a subtree (e.g. "crates/omw-server", "vendor/warp-stripped/app/src/ai_assistant"). User-invoked only — does not auto-trigger.
Walk every Command::new() spawn site in omw_local code and cross-reference against the bundling steps in scripts/build-mac-dmg.sh (and the Windows equivalent). Use BEFORE running a release build script; this is the audit that would have caught the v0.0.3 keychain-helper and Node-on-PATH ship bugs. Argument is the target version.
Verify changes touching crates/omw-remote/ or specs/byorc-protocol.md against the BYORC protocol invariants. Use when reviewing a PR that modifies the remote daemon, the pairing flow, the signed-request validator, or the protocol spec itself. Read-only review aid.
Verify a branch or PR stays inside PRD §3.1 v1.0 Committed Scope. Use when the user wants to check scope drift before opening a PR, when a contributor asks "is this in scope?", or before merging a non-trivial branch.
Walk the pre-release checklist from specs/test-plan.md §7 for a target version. Use when the user is preparing a release (tagging v0.1, v0.2, ..., v1.0), wants to verify release readiness, or asks "are we ready to ship?". Argument is the target version.
Cross-reference PRD ↔ TODO ↔ specs/*.md for drift, broken cross-links, and orphaned bullets. Use when the user asks to verify documentation consistency, after editing PRD or any spec, before publishing the repo, or when proof-reading.
| name | refresh-cassette |
| description | Walk the provider cassette refresh ritual from specs/test-plan.md §4.4. Use when the user explicitly asks to refresh cassettes for a provider, or when CI flags cassette drift. Argument is the provider name (openai, anthropic, openai-compat, ollama). REFUSES to make real API calls unless OMW_CASSETTE_REFRESH=1. |
| tools | Bash, Read |
Guided walkthrough of the cassette refresh procedure for one Tier-1 provider. Real API calls cost real money — this skill is gated behind an explicit env var.
Before doing anything:
$ARGUMENTS is empty, prompt for the provider name (openai, anthropic, openai-compat, ollama). Do not pick a default.OMW_CASSETTE_REFRESH=1 is NOT set in the environment, refuse:
"Refusing to run real-API recordings without OMW_CASSETTE_REFRESH=1. Set the env var, then re-run. This safeguard prevents accidental billing."specs/test-plan.md §4.3 to enumerate the required cassette set for $ARGUMENTS. Currently 8 cassettes per provider: simple-response, streaming-with-thinking, tool-call-shell, tool-call-with-fs-write, multi-turn, error-rate-limit, error-malformed, usage-reconciliation.scripts/refresh-cassettes.sh $ARGUMENTS if it exists. (This script is built in v0.1 and will not exist during Phase 0.)If scripts/refresh-cassettes.sh is missing, print this checklist for the human to follow:
Manual cassette refresh — provider: <name>
1. Set provider API key in keychain (or as env var locally).
2. Run the cassette runner in record mode:
OMW_CASSETTE_RECORD=1 cargo test -p omw-provider-<name> --test cassettes
3. Inspect the regenerated JSON files under
crates/omw-provider-<name>/tests/fixtures/cassettes/
4. Verify each cassette covers the 8 required scenarios.
5. Open a PR titled "test(cassettes): refresh <name> Q<n> 20<yy>"
6. Reviewer confirms semantic equivalence per test-plan.md §4.4.