ship-checklisted

Run the full post-implementation review pipeline: pr-review -> fresh-eyes -> code-quality -> test-audit -> bug-check -> pr-monitor. Phases 1-5 run as dedicated agent types (ship-check plugin) with skills preloaded — genuine fresh eyes with no inherited context. Phase 6 (pr-monitor) runs inline for user interaction. Use when asked to "ship check", "review pipeline", "full review", "run all reviews", or after implementation is complete and ready for review. NOT for: single-dimension review (use the individual skill), quick CI check (use pr-monitor), or post-merge testing (use verify).
aliasunder/agent-plugins · ★ 0 · Code & Development · score 72

Install: claude install-skill aliasunder/agent-plugins

# Ship Check Orchestrate the full review pipeline. Phases 1-5 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. Phase 2 (fresh-eyes) is the exception: it deliberately loads no conventions, no memory, and no shell — only Read/Grep/Glob — so its pauses reflect what a newcomer experiences, not what the project allows. ## Pipeline ``` Phase 1: ship-check:pr-reviewer -> correctness, security, conditional checks Phase 2: ship-check:fresh-eyes -> stranger pauses (report only, no conventions) Phase 3: ship-check:code-quality-reviewer -> convention compliance, readability (resolves Phase 2 pauses) Phase 4: ship-check:test-auditor -> test design, assertion quality, coverage gaps Phase 5: ship-check:bug-checker -> description-vs-code, SQL, type coercion, boundary Phase 6: pr-monitor (inline) -> CI status, bot comment resolution, loop until ready ``` ## Attribution Every piece of text the pipeline posts to a PR — inline review comments, review bodies, PR-level comments, thread replies — MUST include the attribution footer. This applies in ALL modes (default and comment), to ALL participants (phase agents, orchestrator tr