simplify

Review and simplify code changes in a diff against the main branch.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/jonkraatz/claude-skills --skill simplify-jonkraatz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/jonkraatz/claude-skills/tree/main/skills/simplify
Command: npx skills add https://github.com/jonkraatz/claude-skills --skill simplify-jonkraatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain code quality by reviewing and simplifying changes in a diff before merging, focusing on reuse, simplification, efficiency, and abstraction level.

Core Features & Use Cases

  • Merge-Time Quality Pass: Review and simplify changes in a diff against the main branch.
  • Focus on Quality: No behavior changes, no bug-hunting, and no refactors outside the diff scope.
  • Use Case: Before merging a branch or PR, use /simplify to ensure the changes are of high quality and do not introduce new issues.

Quick Start

Run /simplify on the current branch to review and simplify changes.

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I review code quality in a diff before merging to the main branch?

Review code quality in a diff by analyzing changes against the main branch to focus on reuse, efficiency, and abstraction level. This ensures no behavior changes or bugs are introduced during the merge process.

What is the best way to simplify code changes without altering existing behavior?

Simplify code changes without altering behavior by reviewing the diff against main to focus purely on reuse and abstraction level. The process explicitly avoids bug-hunting and refactors outside the diff scope.

Can I use diff analysis to improve code abstraction levels before a pull request?

Diff analysis can improve code abstraction levels before a pull request by reviewing changes against the main branch. It focuses on simplification and efficiency while ensuring no behavior changes are introduced.

Does merge-time code review check for bugs outside the current diff scope?

Merge-time code review does not check for bugs outside the current diff scope. It strictly focuses on simplifying the changes in the diff against main, ensuring no behavior changes or new bugs are introduced during the merge.

When do I need to run a focused code review for refactoring and efficiency?

Run a focused code review for refactoring and efficiency before merging a branch or pull request. This ensures the changes in the diff are of high quality and do not introduce new issues to the main branch.