simplify

Name: simplify
Availability: InStock
Author: uniquecrete

Refactor recently modified source code for clarity while preserving exact functionality.

Updated May 6, 2026

Search Tags:#typescript #code review #refactoring #readability #maintainability #project standards #code simplification

Ready to run

npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill simplify-uniquecrete

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: simplify
Source: https://github.com/Uniquecrete/ThinkFasterv1/tree/main/Skills/simplify
Command: npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill simplify-uniquecrete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes accidental complexity from recently changed code, making it clearer and easier to maintain while preserving the exact same functionality and outputs.

Core Features & Use Cases

Preserve functionality: Refactors only how the code is written, not what it does, including features, results, and behaviors.
Apply project standards: Uses the repository’s established conventions (e.g., ES modules, import sorting/extensions, React Props typing, and consistent error-handling patterns when applicable).
Increase clarity: Reduces unnecessary nesting, removes redundant abstractions, improves naming, and avoids hard-to-read constructs like nested ternaries in favor of clearer control flow.
Focus on scope: Prioritizes recently modified/touched code unless a broader review is explicitly requested.

Quick Start

Use the simplify skill to review the file you just edited and refine it for clarity and consistency while keeping behavior identical.

Frequently Asked Questions about simplify

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

FAQPage Schema

How do I clean up TypeScript code without changing its behavior?▼

To clean up TypeScript code without changing behavior, you refactor recently modified files for clarity and consistency while strictly preserving features, outputs, and control flow. This removes accidental complexity and aligns the source with project standards.

What is the best way to refactor nested ternaries for better readability?▼

Refactoring nested ternaries for readability involves replacing hard-to-read constructs with clearer control flow and reduced nesting. This code simplification improves maintainability while ensuring the exact functionality and outputs remain completely unchanged.

Does this code review tool enforce project import conventions and typing patterns?▼

Yes, code review enforces project import conventions and typing patterns by applying the repository’s established standards. It checks ES module usage, import sorting, and React Props typing to ensure consistency during post-edit cleanup.

Can I run a broad code style review across an entire project instead of just modified files?▼

You can run a broad code style review across an entire project, but the default scope prioritizes recently modified or touched code. A broader review for readability and maintainability must be explicitly requested to move beyond recent changes.

When should I not use scoped refactoring on recently changed source files?▼

You should avoid scoped refactoring when strict behavior preservation cannot be verified, as the process demands that outputs and features remain identical. It focuses on structural clarity, so any required functional changes need separate handling.