addy-code-simplification

Refactors code to reduce complexity while preserving exact behavior and project conventions.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill addy-code-simplification-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: addy-code-simplification
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/addy-code-simplification
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill addy-code-simplification-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working code often accumulates unnecessary complexity—deep nesting, long functions, unclear names, and duplication—that makes it harder to read, maintain, and extend. This Skill provides a disciplined, behavior-preserving process for simplifying code without introducing regressions. ## Core Features & Use Cases - Five Simplification Principles: Preserve behavior exactly, follow project conventions, prefer clarity over cleverness, avoid over-simplification, and scope changes to what changed. - Pattern Detection Tables: Concrete signals for structural complexity, naming issues, and redundancy, each paired with a specific simplification technique. - Language-Specific Guidance: Before/after examples for TypeScript, JavaScript, Python, and React/JSX covering common verbosity patterns. - Use Case: After shipping a feature with passing tests, run a simplification pass to flatten nested conditionals into guard clauses, rename generic variables like data and temp, and extract duplicated logic—verifying tests still pass after each incremental change. ## Quick Start Ask the agent to simplify the recently modified functions in your current file while keeping all tests passing and behavior unchanged.

Frequently Asked Questions about addy-code-simplification

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

FAQPage Schema
How do I refactor code for readability without changing behavior?▼

Apply one simplification at a time—extract guard clauses from deep nesting, split long functions, rename generic variables—then run the test suite after each change. If tests fail, revert that change and reconsider before proceeding.

How to simplify deeply nested conditionals in Python or TypeScript?▼

Replace nested if-blocks with guard clauses that handle error and edge cases first via early returns, leaving the happy path flat at the end. This reduces nesting depth while preserving identical error behavior and ordering.

When should I not simplify or refactor code?▼

Avoid simplifying code you do not yet understand, performance-critical code where the simpler version is measurably slower, code about to be rewritten entirely, and code already clean. Also avoid drive-by refactors outside the current task's scope.

Does code simplification require modifying existing tests?▼

No. Simplification must preserve behavior exactly, so all existing tests should pass without modification. If a change requires editing tests to pass, it likely altered behavior and should be reverted.

Should refactoring and feature changes be in the same commit?▼

No. Submit refactoring separately from feature or bug fix changes. Mixed changes are harder to review, revert, and understand in history, and batching simplifications makes it impossible to identify which one caused a failure.