simplify

Reviews changed code for reuse, quality, and efficiency, then fixes issues found.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill simplify-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/2026-09-10/simplify
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill simplify-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After making code changes, it is easy to introduce duplicated logic, hacky patterns, and performance regressions that slip past a quick self-review. This Skill automates a structured post-change review so issues are caught and fixed before they accumulate. ## Core Features & Use Cases - Three Parallel Review Agents: Launches concurrent agents covering code reuse (duplicate utilities), code quality (redundant state, parameter sprawl, stringly-typed code), and efficiency (N+1 patterns, missed concurrency, memory leaks). - Git-Diff Driven Scope: Uses git diff to identify exactly what changed, falling back to recently modified files when no git changes exist. - Automatic Fixing: Aggregates all findings and fixes each issue directly, skipping false positives without debate. - Use Case: After implementing a new feature across several files, run this Skill to have three reviewers inspect the diff in parallel and clean up duplicated helpers, unnecessary re-renders, and sequential async calls before committing. ## Quick Start Review my current uncommitted changes for reuse, quality, and efficiency problems and fix whatever you find.

Frequently Asked Questions about simplify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes for quality issues automatically?

Run this Skill after making changes; it inspects the git diff and launches three parallel review agents covering reuse, quality, and efficiency. Findings are aggregated and fixed directly, with false positives skipped.

What code quality problems does an automated review catch?

It catches redundant state, parameter sprawl, copy-paste duplication, leaky abstractions, stringly-typed code, and unnecessary JSX nesting. It also flags duplicated functionality that should reuse existing utilities in the codebase.

How does the review decide which files to check?

It runs git diff (or git diff HEAD with staged changes) to identify changed files. If there are no git changes, it falls back to the most recently modified files mentioned or edited earlier in the conversation.

Can automated review detect performance problems in code changes?

Yes, the efficiency agent flags redundant computations, N+1 patterns, missed concurrency, hot-path blocking work, no-op state updates, TOCTOU existence checks, memory leaks, and overly broad file or data operations.

What happens when a review finding is a false positive?

False positives or findings not worth addressing are noted and skipped without argument. The Skill fixes legitimate issues directly and ends with a brief summary of what was fixed or confirms the code was already clean.