ship-checklisted

# Ship Check Orchestrate the full review pipeline. Phases 1-4 dispatch **dedicated agent types** from the ship-check plugin (not forks) so each reviewer approaches the code as a genuine stranger — no inherited context, no authorship bias. Each agent has its review skill and fable-mode preloaded via the `skills:` frontmatter, and loads project conventions (CLAUDE.md, AGENTS.md, CLAUDE.local.md) and vault memory independently. ## Pipeline ``` Phase 1: ship-check:pr-reviewer -> correctness, security, conditional checks Phase 2: ship-check:code-quality-reviewer -> convention compliance, readability Phase 3: ship-check:test-auditor -> test design, assertion quality, coverage gaps Phase 4: ship-check:bug-checker -> description-vs-code, SQL, type coercion, boundary Phase 5: pr-monitor (inline) -> CI status, bot comment resolution, loop until ready ``` ## Before starting 1. Confirm a PR exists for the current branch (or that changes are committed and pushed). If not, ask the user whether to commit/push first. 2. Identify the base branch (usually `main`). 3. Get the PR number and branch name — agents need this context in their briefing. ## Comment mode (`--comment`) When `--comment` is active, the entire pipeline switches from fix-and-push to review-and-comment. Each phase posts findings as inline PR review comments via `gh api` instead of editing files. Phase 5 (pr-monitor) is skipped entirely — the pipeline is reviewing a PR it isn'