sakura-simplify

Reduce code duplication, dependencies, and structural complexity while preserving accepted software behavior.

3|1|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-simplify-v20227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sakura-simplify
Source: https://github.com/v20227/using-sakura-dev/tree/main/skills/sakura-simplify
Command: npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-simplify-v20227

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate duplicate implementations, dead code, unnecessary dependencies, and tangled responsibilities over time, making them harder to understand and change. This Skill performs bounded, evidence-based refactoring that reduces structural overhead without altering accepted behavior, public interfaces, or security boundaries. ## Core Features & Use Cases - Overhead Detection: Distinguishes real handwritten-source complexity from generated output, dependencies, and assets, and verifies dynamic callers before treating code as dead. - Behavior-Preserving Refactoring: Merges duplicate rules, splits mixed responsibilities along existing feature boundaries, and removes superseded implementations only after proving replacements work. - Verified Results: Reruns checks and representative user paths after changes, compares before/after evidence with the same measurement scope, and stops once the scoped overhead is removed. - Use Case: You notice a project has grown unwieldy with repeated logic across modules. Ask for a structure cleanup, and the Skill identifies high-confidence duplication, refactors it in recoverable steps, and proves existing behavior still works. ## Quick Start Ask the assistant to simplify this project's structure by removing duplication and dead code while keeping all existing features working.

Frequently Asked Questions about sakura-simplify

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

FAQPage Schema
How do I reduce code duplication without breaking existing features?▼

Establish current checks and representative user behavior before editing, then merge duplicate rules only when their semantics and ownership truly match. Rerun tests and user paths after each change to confirm behavior is preserved.

How to safely remove dead code from a project?▼

Trace frontend routes, backend entrypoints, dynamic loading, and framework conventions before treating a symbol as unreferenced. Static search alone cannot prove the absence of dynamic callers, so preserve unresolved candidates and document missing evidence.

Does refactoring change public APIs or data formats?▼

No. Feature removal, public API changes, and data-format changes are treated as product decisions, not cleanup details. The Skill preserves accepted behavior, interfaces, validation, permission checks, and error handling throughout.

When should I not use automated code simplification?▼

Avoid it for routine feature work, release-file cleanup, or whole-repository rewrites driven by line-count targets. It is meant for bounded, evidence-backed structural improvements, not subjective polish or framework migrations.

Why does removing a dependency require more than deleting it?▼

Dependencies can be used by build, test, runtime, or plugin paths that are not obvious from imports. The manifest and authoritative lockfile must be updated through the established package manager after checking all usage.