One-click install
npx skills add https://github.com/rdleclerc/agentic-uber-skills --skill ubersimplify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubersimplify
Source: https://github.com/rdleclerc/agentic-uber-skills/tree/main/ubersimplify
Command: npx skills add https://github.com/rdleclerc/agentic-uber-skills --skill ubersimplify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

Ubersimplify helps teams reduce accidental complexity, dead code, and modularity theater without breaking behavior, by requiring evidence, explicit authorization for patches, and strict rollback and safety gates.

Core Features & Use Cases

  • Default Audit-first workflow: maps complexity, modularity boundaries, dead/dynamic references, and agent-affordance risks without editing.
  • Proof-gated Patch Mode: permits small reversible simplification batches only after explicit authorization and strong local evidence (including characterization tests when confidence is medium).
  • Detailed simplification trail & report contract: produces candidates, patch logs, rollback plans, and an evidence-backed final verdict suitable for downstream acceptance and learning.

Quick Start

Use the ubersimplify skill in Audit mode to inspect this codebase for overcomplication and propose a proof plan without editing files.

Frequently Asked Questions about ubersimplify

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

FAQPage Schema
How do I audit dead code and unnecessary complexity in my codebase without breaking existing behavior?

Codebase simplification audits map modularity boundaries and dead code safely by defaulting to audit-first mode, which inspects complexity without editing files and requires explicit authorization before applying any patches.

What is the safest way to plan a modularity refactor that can be easily rolled back?

A safe modularity refactor requires an explicit rollback plan, detailed patch logs, and documented test confidence to ensure all simplification changes are reversible and justified by evidence.

How do I prove the impact of a code cleanup and deletion before executing the changes?

You prove cleanup impact by generating an evidence-backed final verdict, candidate simplification proposals, and rollout proof reports that document test confidence and justify each deletion.

Can I use automated code simplification on agentic systems with dynamic references?

Yes, automated simplification supports agentic systems bloat scenarios by applying dead-code dynamic-reference safeguards and mode-aware constraints to prevent accidental deletion of actively used agent components.

When should I not use automated codebase simplification tools for refactoring?

You should avoid automated simplification when local evidence confidence is medium without characterization tests, or when explicit authorization is absent, as the proof-gated patch mode strictly blocks unsafe deletions.

Does ubersimplify automatically edit files when scanning for modularity issues and dead code?

No, ubersimplify enforces explicit no-auto-trigger behavior by using an audit-first workflow that maps complexity and proposes a proof plan without modifying any codebase files.