release-checklist

スター12

フォーク5

更新日2026年4月29日 07:26

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 ページを確認してインストールできます。

ソース

AndrewWayne

AndrewWayne/oh-my-warp

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Release Checklist

Walks the pre-release checklist defined in specs/test-plan.md §7 for the version passed as $ARGUMENTS. Reports per-item status. Read-only.

Procedure

If $ARGUMENTS is empty, prompt for a target version (e.g. v0.1, v0.4, v1.0). Do not pick a default.
Read specs/test-plan.md §7 (pre-release checklist) and §8 (per-phase commitments) to get the version-specific checks.
For each item in the checklist:
- All Tier A green on the release commit — run git log --oneline -1 and check the latest CI status if accessible, else prompt the user to confirm.
- Tier B green for past 7 nights — read CI history if accessible, else prompt.
- Manual omw provider test — print: "Run manually with maintainer's real keys. Confirm green."
- Homebrew clean-install (v1.0+) — print VM checklist.
- Real-Tailscale + real-phone smoke (v0.4+) — print manual checklist.
- Upstream rebase smoke green for past 7 nights — read CI history.
- No open sev-1 tracking issues — gh issue list --label sev-1 --state open if gh available.
- CHANGELOG.md updated — git log since last tag vs CHANGELOG diff.
- External review sign-off — read specs/byorc-protocol.md (v0.4) or v1.0 review record if present.
For each item, mark: ✓ pass, ✗ fail, ? needs-human-confirm.
Print a summary verdict.
Do NOT cut tags, push, or run release tooling. This skill is advisory only.

Output format

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)

Notes

During Phase 0 / v0.1 this skill will report mostly ? because CI infra isn't built yet. That's expected.
If a checklist item is N/A for the target version (e.g. Homebrew for v0.1), mark it explicitly N/A rather than ✓ or ✗.

このリポジトリの他の Skills

同じリポジトリ

tech-debt-audit

AndrewWayne/oh-my-warp

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.

2026-05-0812

release-build-audit

AndrewWayne/oh-my-warp

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.

2026-05-0712

byorc-protocol-check

AndrewWayne/oh-my-warp

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.

2026-04-2912

check-scope

AndrewWayne/oh-my-warp

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.

2026-04-2912

refresh-cassette

AndrewWayne/oh-my-warp

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.

2026-04-2912

spec-consistency

AndrewWayne/oh-my-warp

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.

2026-04-2912

Release Checklist

Walks the pre-release checklist defined in specs/test-plan.md §7 for the version passed as $ARGUMENTS. Reports per-item status. Read-only.

Procedure

If $ARGUMENTS is empty, prompt for a target version (e.g. v0.1, v0.4, v1.0). Do not pick a default.

Read specs/test-plan.md §7 (pre-release checklist) and §8 (per-phase commitments) to get the version-specific checks.

For each item in the checklist:

All Tier A green on the release commit — run git log --oneline -1 and check the latest CI status if accessible, else prompt the user to confirm.
Tier B green for past 7 nights — read CI history if accessible, else prompt.
Manual omw provider test — print: "Run manually with maintainer's real keys. Confirm green."
Homebrew clean-install (v1.0+) — print VM checklist.
Real-Tailscale + real-phone smoke (v0.4+) — print manual checklist.
Upstream rebase smoke green for past 7 nights — read CI history.
No open sev-1 tracking issues — gh issue list --label sev-1 --state open if gh available.
CHANGELOG.md updated — git log since last tag vs CHANGELOG diff.
External review sign-off — read specs/byorc-protocol.md (v0.4) or v1.0 review record if present.

For each item, mark: ✓ pass, ✗ fail, ? needs-human-confirm.

Print a summary verdict.

Do NOT cut tags, push, or run release tooling. This skill is advisory only.

Output format

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)

Notes

During Phase 0 / v0.1 this skill will report mostly ? because CI infra isn't built yet. That's expected.

If a checklist item is N/A for the target version (e.g. Homebrew for v0.1), mark it explicitly N/A rather than ✓ or ✗.

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