القائمة
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.
التثبيت باستخدام 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 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.
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 | release-checklist |
| description | 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. |
| tools | Bash, Read, Grep |
Walks the pre-release checklist defined in specs/test-plan.md §7 for the version passed as $ARGUMENTS. Reports per-item status. Read-only.
$ARGUMENTS is empty, prompt for a target version (e.g. v0.1, v0.4, v1.0). Do not pick a default.specs/test-plan.md §7 (pre-release checklist) and §8 (per-phase commitments) to get the version-specific checks.git log --oneline -1 and check the latest CI status if accessible, else prompt the user to confirm.omw provider test — print: "Run manually with maintainer's real keys. Confirm green."gh issue list --label sev-1 --state open if gh available.git log since last tag vs CHANGELOG diff.specs/byorc-protocol.md (v0.4) or v1.0 review record if present.Release checklist — target: <version>
Phase commitments (test-plan.md §8 for <version>):
[✓|✗|?] <commitment>
Pre-release checklist (test-plan.md §7):
[✓|✗|?] All Tier A green on release commit
[✓|✗|?] Tier B green past 7 nights
[✓|✗|?] Manual provider test (Tier-1 × 4)
[✓|✗|?] Homebrew clean-install (v1.0+)
[✓|✗|?] Real-Tailscale + phone smoke (v0.4+)
[✓|✗|?] Upstream rebase smoke past 7 nights
[✓|✗|?] No open sev-1 tracking issues
[✓|✗|?] CHANGELOG updated
[✓|✗|?] External review sign-off
Verdict: READY | NOT READY (N items failing)
? because CI infra isn't built yet. That's expected.