simplify-code

Featured

Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.

AI & Automation 39,350 stars 6386 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Simplify Code Review changed code for reuse, quality, efficiency, and clarity issues. Use Codex sub-agents to review in parallel, then optionally apply only high-confidence, behavior-preserving fixes. ## When to Use - When the user asks to simplify, clean up, refactor, or review changed code. - When you want high-confidence, behavior-preserving improvements on a scoped diff. ## 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...

Details

Author
sickn33
Repository
sickn33/antigravity-awesome-skills
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

simplify-code

Run a multi-agent review of changed files for reuse, quality, efficiency, and clarity issues followed by automated fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

314 Updated today
tobihagemann
AI & Automation Solid

simplify

Review changed code for reuse, quality, and efficiency. Fix any issues found.

42 Updated 2 days ago
MiaoDX
Code & Development Listed

code-review-simplify

Use when reviewing code changes for quality, security, performance, or maintainability issues and identifying simplification opportunities in a single token-efficient pass

1 Updated today
mickeyyaya
Code & Development Listed

ai-simplify

On-demand code simplification — guard clauses, method extraction, nesting flattening, dead code removal, conditional simplification. Behavior preserved; tests pass after every change. Scoped to operator-chosen files or current diff. No PR, no auto-commit. Trigger for 'simplify this file', 'reduce complexity here', 'clean up the in-flight diff', 'flatten this nesting'. Not for scheduled repo-wide sweeps — use /ai-simplify-sweep. Not for structural changes (file moves, renames) — use /ai-refactor.

49 Updated today
arcasilesgroup
Code & Development Listed

review-code

Review the current git diff and produce DRIFT.md when a sprint context exists. **Mandatory before /magi:commit in sprint mode** — DRIFT.md is required input for the commit step's drift backfill flow. Default behaviour is multi-CLI MAGI cross-review (orchestrator + magi-consensus). Use --single to fall back to a single Opus reviewer (the magi-reviewer subagent) — saves tokens but loses cross-validation. Supports --magi <mode> override and --reviewers override. Never auto-fixes; always presents findings for the user to decide.

1 Updated today
bozkurtonur3-lgtm