Agent skill · software engineering · 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.
Why this skill is useful
Adds specific commands and procedures for reviewing and simplifying code changes that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Review and Simplify Changes When to Use 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. Modes Choose the mode from the user's request: review-only: user asks to review, audit, or check the changes safe-fixes: user asks to simplify, clean up, or refactor the changes fix-and-validate: same as safe-fixes, but also run the smallest relevant validation after edits If the user does not specify, default to: review-only for "review", "audit", or "check" safe-fixes for "simplify", "clean up", or "refactor" Step 1: Determine the Scope and Diff Command Prefer this scope order: 1. Files or paths explicitly named by the user 2. Current git changes 3. Files edited earlier in the current Codex turn 4. Most recently modified tracked files, only if the user asked for a review but there is no diff 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: unstaged work: git diff staged work: git diff --cached branch or commit comparison explicitly requested by the user: use that exact diff target mixed staged and unstaged work: review both Do not assume git diff HEAD is the right default when a smaller diff is available. Before reviewing standards or applying fixes, read the repo's local instruction files and relevant project docs for the touched area. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/review-and-simplify-changes--7dd48d