simplify

Refactor freshly changed code within a git diff without altering behavior.

121|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill simplify-agentsystemlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/simplify
Command: npx skills add https://github.com/AgentSystemLabs/core --skill simplify-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It cleans up freshly-changed code by reducing duplication, removing smells, and refactoring for readability and maintainability without changing behavior.

Core Features & Use Cases

  • Diff-driven refactoring: reviews the git diff (by default, changed files vs the merge-base) to target what actually changed.
  • DRY and code-smell detection: flags duplication, magic numbers, poor naming, tight coupling, oversized units, and inefficient patterns.
  • Safety-net for behavioral changes: runs a test-first gate when structural refactors could alter behavior, and defaults to mechanical-only changes when no test net is available.

Quick Start

Ask your agent to simplify a small set of recently modified files by routing the request with the phrase "simplify".

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I refactor freshly changed code without changing its behavior?

To refactor freshly changed code safely, review the git diff to target only what actually changed, gate structural refactors behind a test net, and apply mechanical-only changes when no tests are available.

What is the best way to detect code smells and DRY violations in a focused git diff?

Detecting code smells and DRY violations in a focused git diff involves scanning changed files versus the merge-base to flag duplication, poor naming, tight coupling, and inefficient patterns within that specific scope.

Can I clean up code automatically after addressing PR comments or fixing bugs?

Yes, you can clean up code after addressing PR comments or fixing bugs by performing smell reviews over the git diff and supporting safe auto-application of mechanical improvements within the changed scope.

Do I need a test safety net to apply structural refactoring to my codebase?

A test safety net is required to gate structural refactors that could alter behavior, but when no test net is available, the process defaults to mechanical-only changes to ensure safety.

What types of code improvements can I apply to recently modified files?

You can apply code improvements to recently modified files by reducing duplication, removing smells, refactoring for readability, and ensuring less coupling to produce a smaller and drier version.