Menü
Orchestrate the mandatory completion sequence before merging a C# feature — /verify, /deep-review, fix findings, /review-codex, then close the issue and update docs + CHANGELOG.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | ship |
| description | Orchestrate the mandatory completion sequence before merging a C# feature — /verify, /deep-review, fix findings, /review-codex, then close the issue and update docs + CHANGELOG. |
| argument-hint | ["feature-name"] |
Run the mandatory completion sequence from CLAUDE.md "Completion Workflow" end-to-end. This skill exists because the sequence is prose in CLAUDE.md and steps get silently skipped — the RCA history (docs/reviews/rca-crash-report-2026-05-25.md) shows a 60-file feature shipped with unfixed HIGH/MED findings because Phases 2 and 4 were skipped.
/verify — build + tests must pass. If red, stop and fix./deep-review $ARGUMENTS — 5+ parallel agents (standards, compat, efficiency, completeness, data-flow; C++ checks auto-fire if .cpp/.h in scope). It triages findings spec-compliance-first (see docs/ai-includes/agent-teams.md)..claude/skills/deep-review/SKILL.md)./review-codex — writes the prompt and dispatches Codex via codex exec in the background; tells the user the 10–45 min window once./review-codex again against the post-fix diff. Verify + fix. Write the Phase 3e RCA for every confirmed bug (not just HIGH — see .claude/rules/harness-facts.md)./verify — final build + tests green./issue). Close it with the final commit — do NOT create it retroactively.docs/features/<name>.md.CHANGELOG.md./review-codex and /codex-verify cost real money — confirm with the user before Phase 2 unless they already authorized the ship.Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.