From ship
Reviews and cleans up code using Codex with adversarial challenge (critic-audit), applies fixes directly, then runs cleanup. For quick code polishing and removing slop.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ship:polish [target scope]When to use
整理して, きれいにして, コード整理, slop除去, ポリッシュ, テスト整理, テスト監査, Codex レビュー
[target scope]opusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Codex reviews the diff, then `critic-audit` puts the findings through an adversarial challenge. Fix the survivors, then clean up with `/simplify` and `enhancer-code`. Do not stop at a findings report; apply the fixes directly. For an internal-reviewer audit, use `/audit`.
Codex reviews the diff, then critic-audit puts the findings through an adversarial challenge. Fix the survivors, then clean up with /simplify and enhancer-code. Do not stop at a findings report; apply the fixes directly. For an internal-reviewer audit, use /audit.
$ARGUMENTS may contain the target scope. If empty, analyze git diff HEAD (staged and unstaged changes).
Run an external Codex review to produce findings. If which codex fails, skip to Phase 3.
Run codex review "Review for logic, architecture, data flow, and code simplicity (flag over-complexity and unnecessary indirection)". In codex 0.141.0 the scope flags (--uncommitted / --base / --commit) are mutually exclusive with the PROMPT argument, so pass no scope flag when sending the simplicity-lens PROMPT. Codex reads git status itself and reviews the staged, unstaged, and untracked changes. Omitting the PROMPT falls back to Codex's default review and drops the simplicity lens, so always pass it.
critic-audit filters Codex false positives, then the surviving findings are fixed directly.
critic-audit input schema (critic-audit § Input) and spawn Task(subagent_type: "critic-audit") once with the full list. Wait for the per-finding verdictgit diff scopegit stash any fix that breaks tests| Verdict | Action |
|---|---|
| confirmed | Keep as a fix candidate |
| disputed | Drop |
| downgraded | Apply the lowered severity |
| needs_context | Surface to the user with a one-line summary |
Two cleanup mutators run in sequence on the post-Phase-2 diff, then validate. Both apply fixes directly without a critic-audit challenge, since neither hunts bugs.
Skill("simplify") on the current diff for a cleanup-only pass (reuse, simplification, efficiency, altitude). If it rejects a no-arg invocation, pass the diff scope Phase 1 detectedenhancer-code via Task(subagent_type: "enhancer-code") to remove AI slop and apply simplification rules, then audit tests. Run it after /simplify so its preservation rule (when in doubt, keep) takes priority over /simplify's editsgit stash the cleanup edits on failureReport what each phase did. Codex findings (Phase 1), critic-audit verdict counts and fixes applied with skip reasons (Phase 2), and /simplify plus enhancer-code edits with file:line and the test validation result (Phase 3).
| Error | Action |
|---|---|
| No changes in diff | Report that there is nothing to polish |
codex review fails | Skip to Phase 3 with no findings |
critic-audit fails or returns empty | Keep all findings as confirmed, proceed to fix |
/simplify unavailable or fails | Skip to enhancer-code |
npx claudepluginhub thkt/dotclaude --plugin shipReviews a diff for code reuse, quality, and clarity issues, then optionally applies high-confidence, behavior-preserving fixes using parallel sub-agents.
Polishes code changes before PR by recovering branch context, checking against codebase guidelines for changed files, removing AI slop like extra comments and casts, and final review.
Cross-model review using OpenAI Codex to independently verify plans or code diffs, iterating up to 5 rounds. Useful for architecture decisions, non-trivial refactors, and critical config changes.