Review And Simplify Changes
Dimillian/Skills
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.
Reviews your uncommitted diff with three parallel passes for reuse, quality and efficiency, then applies the straightforward cleanups before a pull request.
Install Simplify Recent Changes
$ npx skills add QwenLM/qwen-code --skill simplify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install QwenLM/qwen-code simplify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/src/skills/bundled/simplify .claude/skills/simplify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "simplify" agent skill from https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplify into .claude/skills/simplify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add QwenLM/qwen-code --skill simplify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install QwenLM/qwen-code simplify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/src/skills/bundled/simplify .agents/skills/simplify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "simplify" agent skill from https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplify into .agents/skills/simplify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add QwenLM/qwen-code --skill simplify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install QwenLM/qwen-code simplify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/src/skills/bundled/simplify .cursor/skills/simplify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "simplify" agent skill from https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplify into .cursor/skills/simplify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/QwenLM/qwen-code.git --path packages/core/src/skills/bundled/simplify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add QwenLM/qwen-code --skill simplify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install QwenLM/qwen-code simplify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/src/skills/bundled/simplify .gemini/skills/simplify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "simplify" agent skill from https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplify into .gemini/skills/simplify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install QwenLM/qwen-code simplifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add QwenLM/qwen-code --skill simplify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/src/skills/bundled/simplify .github/skills/simplify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "simplify" agent skill from https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplify into .github/skills/simplify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add QwenLM/qwen-code --skill simplify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install QwenLM/qwen-code simplify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/src/skills/bundled/simplify .opencode/skills/simplify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "simplify" agent skill from https://github.com/QwenLM/qwen-code/tree/main/packages/core/src/skills/bundled/simplify into .opencode/skills/simplify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
simplify- GitHub stars
- 28k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 720 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Reviews your uncommitted diff with three parallel passes for reuse, quality and efficiency, then applies the straightforward cleanups before a pull request.
- Works in 5 steps: Identify the review scope → Launch three review passes in parallel → Aggregate findings → …
- Cleaning up right after finishing an implementation, before opening a PR
- SKILL.md covers Step 1: Identify the review…, Step 2: Launch three review…, Step 3: Aggregate findings and Step 4: Apply straightforward…, plus 2 more sections
- Calls git
What it does
To decide what to review, the agent checks git state in order: staged changes are diffed against `HEAD`, otherwise the plain uncommitted diff is used, then `git ls-files --modified --others --exclude-standard` so ignored folders like `node_modules` stay out, and last the files edited in the current conversation. If nothing turns up, it stops and says there is nothing to simplify.
Three read-only review passes then run at once as subagents that each read the diff themselves: one hunts for duplicated logic and helpers that already exist, one for maintainability issues such as copy-paste variants, parameter sprawl and redundant state, and the third for efficiency. The findings are merged and the straightforward fixes are applied directly in a later step, rather than only listed as comments.
When your agent uses it
- Cleaning up right after finishing an implementation, before opening a PR
- Polishing recent edits for duplicated logic and awkward APIs
- Asking for a focused simplification pass on one part of a change
Example prompts
- “/simplify tidy up what I changed before I open the pull request”
- “/simplify focus on the error handling in the new parser”
- “Do a cleanup pass over my uncommitted changes before I open the PR.”
Requirements
- A git repository with recent changes, or files edited in the session
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4970bfa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Simplify Recent Changes loads about 1.3k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 720 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from QwenLM/qwen-code at commit 4970bfa, republished under its Apache-2.0 licence (© QwenLM). 720 words, ~1,311 tokens.
Download SKILL.mdSave it as
.claude/skills/simplify/SKILL.md (or your agent's skills folder).- name
- simplify
- 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>`.
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.
- First inspect the current git state.
- If there are staged changes, review against
HEADso both staged and unstaged tracked changes are included. - Otherwise review the current uncommitted diff.
- If there is no git diff, fall back to
git ls-files --modified --others --exclude-standardso the scope respects.gitignore(this keeps build output,node_modules, and other ignored paths out of the cleanup). - If that is still empty, fall back to files edited in this conversation.
- 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-onlygit diff --staged --name-onlygit diff HEAD --name-onlygit diffgit diff HEADgit 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
Look for opportunities to reduce duplication and reuse existing code:
- existing utilities or helpers that should be reused
- duplicated logic introduced in new code
- inline logic that should delegate to an existing abstraction
- ad-hoc helpers for string, path, env, parsing, or type checks when a project utility already exists
Pass 2: Code Quality Review
Look for maintainability issues:
- copy-paste variants that should be unified
- parameter sprawl or awkward APIs
- redundant state or indirection
- abstraction leaks
- stringly-typed code that should be modeled more clearly
- unnecessary nesting
- unnecessary comments that explain what instead of why
- naming or structure that does not match surrounding code
Show full SKILL.md (304 more words)Show less
Pass 3: Efficiency Review
Look for wasteful work and unnecessary overhead:
- repeated work that can be memoized, cached, or removed
- serial work that can be parallelized safely
- unnecessary scans, allocations, reads, or traversals
- hot-path blocking work
- redundant no-op updates
- overly broad operations when a narrower one would work
- existence-check patterns that introduce TOCTOU style waste or risk
Step 3: Aggregate findings
Wait for all three passes to finish, then merge overlapping findings.
Prioritize fixes that are:
- low risk
- local in scope
- clearly aligned with existing project patterns
- easy to validate with tests or targeted commands
Do not force a cleanup if it would require speculative architectural changes.
Step 4: Apply straightforward improvements
Directly implement safe cleanup improvements.
Examples of good automatic fixes:
- replace duplicated logic with an existing helper
- remove redundant code, but only after a repository-wide search confirms it has no remaining callers
- simplify conditionals or control flow
- tighten loops or repeated work
- reduce unnecessary state or wrapper code
- remove low-value comments
- align code with nearby conventions
Skip items that are uncertain, risky, or too invasive. Do not spend time debating rejected findings; simply move on.
Step 5: Verify the cleanup
After making changes:
- Run focused tests for the changed area when they exist.
- Run the relevant project quality checks you can identify for the touched code.
- If there are no applicable tests, at least run a targeted build, typecheck, or lint command that covers the edited files.
Prefer targeted verification over whole-repo commands unless the project only exposes repo-wide checks.
Additional focus
If the user supplied extra instructions after /simplify, treat them as additional review focus and prioritize them alongside the default dimensions.
The raw user invocation appears below when present. Use it to extract any extra focus such as performance, duplication, rendering, API clarity, testability, or naming consistency.
© QwenLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/core/src/skills/bundled/simplify of QwenLM/qwen-code.
Open the folder on GitHubat commit 4970bfa
Compare with similar skills
Simplify Recent Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Simplify Recent Changes this skillQwenLM/qwen-code | 28k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Review And Simplify ChangesDimillian/Skills | 4k | — | ~2k | Automated safety check: Pass | MIT | |
| Codebase Health Refactoringkucherenko/jscpd | 6.3k | — | ~2.5k | Automated safety check: Pass | MIT | |
| DRY Refactoring With jscpdkucherenko/jscpd | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Refactortermide/termide | 171 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Absolute Simplifymaddhruv/absolute | 218 | — | ~6.1k | Automated safety check: Pass | MIT |
Similar skills
Codebase Health Refactoring
kucherenko/jscpd
A three-part cleanup guided by jscpd: measure health, then fix duplicated code, remove dead code and simplify the most complex files, finishing by re-measuring the score.
DRY Refactoring With jscpd
kucherenko/jscpd
Removes copy-paste duplication found by jscpd, starting with exact clones and hotspots, then renamed and near-miss copies, using proven refactoring strategies.
Refactor
termide/termide
Full-workspace code quality analysis and refactoring with validation
Absolute Simplify
maddhruv/absolute
A skill your agent uses when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path.
Nv Park And Review
novuhq/novu
Commit local changes as a baseline, hop into a lightweight review worktree, run a thermo-nuclear code quality review scoped to ONLY that commit, commit the resulting refactor as a separate follow-up…
More from QwenLM/qwen-code
All 41 skills in this repoAgent Feature Reproduction
QwenLM/qwen-code
Reproduces a feature from Codex or Claude Code in Qwen Code by running the reference agent under capture, reading the traces, then implementing matching behavior.
Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Qwen Code Desktop Brand Builder
QwenLM/qwen-code
Builds a rebranded Qwen Code desktop package from the Tauri shell using only a brand id and a logo, with sensible derived defaults.
Qwen Code Memory Leak Debugger
QwenLM/qwen-code
Walks through capturing and comparing V8 heap snapshots to find memory leaks in the Qwen Code Node.js CLI, using tmux and the chrome-devtools CLI.
tmux Real User Testing
QwenLM/qwen-code
Drives Qwen Code in a real tmux session the way a user would and saves a readable step-by-step transcript of each screen for maintainers to review.
Related
Works with
Categories
Questions about Simplify Recent Changes
What does Simplify Recent Changes do?
Reviews your uncommitted diff with three parallel passes for reuse, quality and efficiency, then applies the straightforward cleanups before a pull request. To decide what to review, the agent checks git state in order: staged changes are diffed against `HEAD`, otherwise the plain uncommitted diff is used, then `git ls-files --modified --others --exclude-standard` so ignored folders like `node_modules` stay out, and last the files edited in the current conversation. If nothing turns up, it stops and says there is nothing to simplify.
When should I use Simplify Recent Changes?
Simplify Recent Changes fits situations like: cleaning up right after finishing an implementation, before opening a PR; polishing recent edits for duplicated logic and awkward APIs; asking for a focused simplification pass on one part of a change.
How do I install Simplify Recent Changes in Claude Code?
Run `npx skills add QwenLM/qwen-code --skill simplify -a claude-code`. Or copy the skill folder (packages/core/src/skills/bundled/simplify in QwenLM/qwen-code) into .claude/skills/simplify in your project. Claude Code loads it when a task matches its description.
How do I install Simplify Recent Changes in Codex?
Run `npx skills add QwenLM/qwen-code --skill simplify -a codex`. Or copy the skill folder (packages/core/src/skills/bundled/simplify in QwenLM/qwen-code) into .agents/skills/simplify in your project. Codex loads it when a task matches its description.
Can I use Simplify Recent Changes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add QwenLM/qwen-code --skill simplify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/simplify, .gemini/skills/simplify, .github/skills/simplify and .opencode/skills/simplify in your project.
What does Simplify Recent Changes need to run?
Going by SKILL.md and its folder, Simplify Recent Changes needs the command-line tools its instructions call (git). Our summary lists: A git repository with recent changes, or files edited in the session.
Does Simplify Recent Changes access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Simplify Recent Changes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Simplify Recent Changes use?
Simplify Recent Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Simplify Recent Changes use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Simplify Recent Changes?
Skills that share tags, products or a category with Simplify Recent Changes: Review And Simplify Changes (Dimillian/Skills, 4k stars), Codebase Health Refactoring (kucherenko/jscpd, 6.3k stars), DRY Refactoring With jscpd (kucherenko/jscpd, 6.3k stars) and Refactor (termide/termide, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Simplify Recent Changes?
QwenLM (a GitHub organization) maintains it in QwenLM/qwen-code, which has 28,337 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 7, 2026.
Source: QwenLM/qwen-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.