# Simplify

Review recent code changes for reuse, code quality, and efficiency, then directly apply...

- Repository: https://github.com/QwenLM/qwen-code (28858 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add QwenLM/qwen-code --skill simplify -g -a claude-code -y`
Codex: `npx skills add QwenLM/qwen-code --skill simplify -g -a codex -y`
Cursor: `npx skills add QwenLM/qwen-code --skill simplify -g -a cursor -y`
Gemini CLI: `npx skills add QwenLM/qwen-code --skill simplify -g -a gemini-cli -y`

## Description

Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with `/simplify` or `/simplify <focus>`.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Simplify Recent Changes

You are running a structured cleanup workflow over recent code changes. Your goal is not just to comment on the code, but to safely improve it.

## Step 1: Identify the review scope

Determine which files and changes to review.

1. First inspect the current git state.
2. If there are staged changes, review against `HEAD` so both staged and unstaged tracked changes are included.
3. Otherwise review the current uncommitted diff.
4. If there is no git diff, fall back to `git ls-files --modified --others --exclude-standard` so the scope respects `.gitignore` (this keeps build output, `node_modules`, and other ignored paths out of the cleanup).
5. If that is still empty, fall back to files edited in this conversation.
6. If you still cannot identify a meaningful scope, stop and tell the user there are no recent changes to simplify.

Preferred commands:

- `git diff --name-only`
- `git diff --staged --name-only`
- `git diff HEAD --name-only`
- `git diff`
- `git diff HEAD`
- `git status --short`

Use `git diff HEAD` whenever staged changes exist. Otherwise use `git diff`.

## Step 2: Launch three review passes in parallel

Use the `agent` tool and launch all review passes in a single response so they run concurrently. **Set `subagent_type: "general-purpose"` and `run_in_background: false` on every call, each pass must return its findings inline. Do NOT fork them: never set `subagent_type: "fork"`. A fork runs fire-and-forget and never returns its findings, so there would be nothing to aggregate in Step 3.** Each pass must receive the same review scope and diff command. These passes are read-only: each one inspects and reports findings only and must not modify files, all edits happen later in Step 4.

Keep each review prompt short and focused. Do not paste the full diff into the prompt. Tell each pass to read the diff itself and inspect only files relevant to its findings.

### Pass 1: Code Reuse Review

The rest: https://github.com/QwenLM/qwen-code/blob/HEAD/packages/core/src/skills/bundled/simplify/SKILL.md