simplify

Review changed code and propose the smallest safe refactor for reuse and readability.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/BenchAGI/bench-cowork --skill simplify-benchagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/BenchAGI/bench-cowork/tree/main/skills/simplify
Command: npx skills add https://github.com/BenchAGI/bench-cowork --skill simplify-benchagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changed code for reuse, quality, and efficiency, then fix any issues found. Use after writing non-trivial code, before opening a PR, or when the user asks for a cleanup pass. Applies the "smallest safe change" rubric from the Bench monorepo.

Core Features & Use Cases

  • Identify duplicates and refactor for readability to reduce maintenance burden.
  • Enforce the smallest safe change principle to minimize risk during PRs.
  • Provide rationale and suggested diffs to guide improvements.

Quick Start

Analyze the latest change and propose the smallest safe refactor to improve reuse and readability.

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I refactor recently written code to reduce duplication before opening a pull request?

To refactor recently written code before a pull request, you can apply a smallest safe change rubric to identify duplication, improve readability, tighten logic, and generate minimal diffs with clear rationale.

What is the smallest safe change rubric for code review?

The smallest safe change rubric for code review enforces minimal diffs, requires clear rationale for modifications, and mandates safe validation before merging to minimize risk and maintain reuse across modules.

How do I find readability issues and code duplication across modules in a monorepo?

To find readability issues and code duplication across modules in a monorepo, analyze recent changes to identify opportunities to tighten logic and suggest refactors within the smallest safe scope.

Do I need to provide a specific input format for a code cleanup pass?

You do not need a specific input format for a code cleanup pass. Simply analyze the latest changed code or pull request context to propose refactors that improve reuse and maintainability.

When should I avoid using automated code simplification on my recent changes?

You should avoid automated code simplification when changes require large scope modifications outside the smallest safe scope, or when safe validation cannot be performed before opening the pull request.