simplify

Analyze code diffs for reuse, simplification, and efficiency improvements.

10|Updated May 9, 2026
One-click install
npx skills add https://github.com/jcwleo/oh-no-harness --skill simplify-jcwleo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/jcwleo/oh-no-harness/tree/main/plugins/oh-no-harness/skills-claude/simplify
Command: npx skills add https://github.com/jcwleo/oh-no-harness --skill simplify-jcwleo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the accumulation of technical debt and maintainability issues by performing targeted, behavior-preserving cleanup on code changes before they reach the final review stage.

Core Features & Use Cases

  • Quality Cleanup: Automatically identifies opportunities for code reuse, simplification, efficiency improvements, and altitude adjustments.
  • Maintainability Guardrails: Distinguishes between safe, behavior-preserving cleanup and architectural debt that requires human reviewer intervention.
  • Use Case: After implementing a new feature, use this skill to ensure the code follows existing patterns, removes redundant logic, and operates at the correct level of abstraction without altering the verified behavior.

Quick Start

Invoke the simplify skill to perform a quality cleanup pass on the current diff after establishing a behavior lock.

Frequently Asked Questions about simplify

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

FAQPage Schema
How do I perform behavior-preserving code cleanup before final review?

The refactoring process distinguishes between safe, behavior-preserving cleanup and architectural debt requiring human intervention, automatically identifying opportunities for code reuse, simplification, efficiency improvements, and altitude adjustments without altering verified behavior.

How do I automate code refactoring to reduce technical debt in pending changes?

You can invoke the refactoring skill on a current diff after establishing a behavior lock to ensure the code follows existing patterns, removes redundant logic, and operates at the correct level of abstraction without altering verified behavior.

Does code refactoring work without a verified behavior lock?

No, a verified behavior lock is a strict prerequisite. The refactoring mechanism depends on this lock to guarantee that all cleanup modifications remain functionally identical to the original implementation before final review.

What is the difference between safe code cleanup and architectural debt?

Safe code cleanup involves behavior-preserving modifications like reuse and simplification, whereas architectural debt represents deeper structural issues requiring human reviewer intervention rather than automated refactoring passes.

When should I avoid automated code optimization on my current diff?

You should avoid automated code optimization when architectural debt is present, as the cleanup process handles only safe, behavior-preserving modifications and intentionally flags structural issues for human reviewer intervention.