Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/review-and-simplify-changes
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.
Passed 5 of 11 test cases with the skill, and 6 of 11 without it.
3 fixed8 passed either way8 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
If a user prompt says "Simplify `src/helpers/dates.ts` by eliminating copy-paste logic", which operational mode applies and who performs the file edits?
| Checked | Without skill | With skill |
|---|---|---|
| The safe-fixes mode is selected with file edits performed by the main agent. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when you need review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review...
Review changed code for reuse, quality, efficiency, and clarity issues. Use Codex sub-agents to review in parallel, but keep those sub-agents read-only: they should only inspect code and send findings back to the main agent. Only the main agent may apply high-confidence, behavior-preserving fixes.
Choose the mode from the user's request:
review-only: user asks to review, audit, or check the changessafe-fixes: user asks to simplify, clean up, or refactor the changesfix-and-validate: same as safe-fixes, but also run the smallest relevant validation after editsIf the user does not specify, default to:
review-only for "review", "audit", or "check"safe-fixes for "simplify", "clean up", or "refactor"Prefer this scope order:
If there is no clear scope, stop and say so briefly.
When using git changes, determine the smallest correct diff command based on the repo state:
git diffgit diff --cachedDo not assume git diff HEAD is the right default when a smaller diff is available.
test cases passed, vs 6 / 11 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.