ship

Invoke the dotnet-skills:shipping-and-launch skill.

/ship is a fan-out orchestrator. It runs three specialist personas in parallel against the current change, then merges their reports into a single go/no-go decision with a rollback plan. The personas operate independently — no shared state, no ordering — which is what makes parallel execution safe and useful here.

Phase A — Parallel fan-out

Spawn three subagents concurrently using the Agent tool. Issue all three Agent tool calls in a single assistant turn so they execute in parallel — sequential calls defeat the purpose of this command.

In Claude Code, each call passes subagent_type matching the persona's name field:

1. code-reviewer — Run a five-axis review (correctness, readability, architecture, security, performance) on the staged changes or recent commits. Ground findings in .NET specifics: nullable-reference-type honesty, async/await correctness (no .Result / .Wait() on I/O paths), CancellationToken threading, DI lifetime correctness, EF Core N+1, MyApp.Core / MyApp.Infrastructure / MyApp.Contracts layering. Output the standard review template with file.cs:line references.
2. security-auditor — Run a vulnerability and threat-model pass. Check OWASP Top 10 translated to ASP.NET Core / EF Core / Blazor equivalents, secrets handling (dotnet user-secrets / Key Vault / env), auth + policy-based authz ([Authorize], RequireAuthorization(), per-resource IDOR checks), FromSqlRaw injection, and dependency CVEs (dotnet list package --vulnerable --include-transitive). Output the standard audit report.
3. test-engineer — Analyze test coverage for the change. Identify gaps in happy path, edge cases, error paths, cancellation, and concurrency scenarios — framed around the xUnit / MSTest runner the project uses and the relevant integration boundary (WebApplicationFactory<Program>, Testcontainers, Microsoft.Playwright, Avalonia.Headless.XUnit). Output the standard coverage analysis.

In other harnesses without an Agent tool, invoke each persona's system prompt sequentially and treat their outputs as if returned in parallel — the merge phase still works.

Constraints (from Claude Code's subagent model):

• Subagents cannot spawn other subagents — do not let one persona delegate to another.
• Each subagent gets its own context window and returns only its report to this main session.
• If you need teammates that talk to each other instead of just reporting back, use Claude Code Agent Teams and reference these personas as teammate types (see ../references/orchestration-patterns.md).

Persona resolution. If you've defined your own code-reviewer, security-auditor, or test-engineer in .claude/agents/ or ~/.claude/agents/, those take precedence over this plugin's versions — /ship picks up your customizations automatically. This is intentional: plugin subagents sit at the bottom of Claude Code's scope priority table, so user-level definitions win by design.