code-simplifier

Refactor code for readability after green verification passes.

Updated Jan 8, 2026

Search Tags:#readability #maintainability #verification #refactor #code #naming #diffs

Ready to run

npx skills add https://github.com/lightningfastsls/London_Lab --skill code-simplifier-lightningfastsls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-simplifier
Source: https://github.com/lightningfastsls/London_Lab/tree/main/.codex/skills/code-simplifier
Command: npx skills add https://github.com/lightningfastsls/London_Lab --skill code-simplifier-lightningfastsls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams make code easier to read and maintain by performing small, focused refactors after verification has green status, reducing duplication while preserving behavior.

Core Features & Use Cases

Targeted Refactoring: small, readable changes that improve naming, structure, and clarity without changing observable behavior.
Verification-Driven: only runs after the current task passes green verification.
Maintainability Gains: leads to easier reviews and fewer regressions in ongoing projects.

Quick Start

Perform a small, focused refactor only after the latest verification is green, then re-run the verification checks.

Frequently Asked Questions about code-simplifier

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

FAQPage Schema

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

Safe refactoring for readability requires green verification status first, followed by small, focused changes to naming or structure that preserve observable results, and a mandatory re-run of verification checks after edits.

What's the best way to improve code maintainability after passing tests?▼

The best way to improve code maintainability after passing tests is to limit refactoring diffs to small, reviewable steps that reduce duplication and improve naming, ensuring observable behavior remains unchanged throughout the process.

When should I run verification checks during a code refactor?▼

Run verification checks immediately before starting a refactor to confirm green status, and re-run them after edits to confirm structural changes and naming improvements did not alter observable results.

Can I introduce new dependencies when refactoring for readability?▼

No, you must avoid new dependencies when refactoring for readability. The process focuses on reorganizing structure, reducing duplication, and improving naming through small, reviewable diffs without altering observable results.

Why does my code refactor require a green verification status first?▼

Code refactoring requires green verification first to establish a baseline of correct observable behavior, ensuring that subsequent small, focused changes to naming or structure can be safely validated without introducing regressions.