メニュー
Simplify a completed diff before it ships. Use before /ship, after a feature works, or when a change feels over-engineered. Removes unnecessary abstraction, scope creep, dead code introduced by the diff, and confusing structure without changing behaviour.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | simplify |
| description | Simplify a completed diff before it ships. Use before /ship, after a feature works, or when a change feels over-engineered. Removes unnecessary abstraction, scope creep, dead code introduced by the diff, and confusing structure without changing behaviour. |
The diff does the same job with less code, less surprise, and fewer review risks. Behaviour must not change except to remove accidental scope creep.
git diff --stat and inspect changed files. Identify the user-requested behaviour in one sentence.End with:
Shepherd an open PR to merge. Watches CI, fixes failures, addresses review comments, resolves conflicts, and enables/executes merge when green. Use after opening a PR, when the user says babysit/watch/get this merged, or as the final step of /ship.
Visual and UX review for user-visible changes: frontend components, HTML/CSS, templates, dashboards, rendered docs, emails, and CLI output formatting. Use as part of /ship when a diff touches UI/human-facing output. If nothing user-visible changed, explicitly mark not applicable and stop.
Commit, push, and open a pull request for the current change. Use when the user says open a PR, ship this, commit and push, or as the PR creation step of /ship. Requires verification evidence in the PR body.
Take a finished local change to a merged PR through non-negotiable release gates. Use when the user says ship it, /ship, get this merged, release this, or when /coach has a READY local diff. Enforces simplify, verify, design applicability, PR evidence, independent review, CI, and merge babysitting while preserving Anthropic budget where safe.
Prove a change actually works before it ships. Use whenever a change is done, after implementing a feature/fix, before opening a PR, or when the user says verify/check this works/is this actually working. Tests passing is not sufficient; this skill requires real entry-point evidence.