reduce

An abstraction audit identifies indirection points across toolchains, frameworks, and configurations to evaluate their cost versus value. It uses repo-local evidence scoring and a three-score rubric to pinpoint detours caused by unnecessary tooling or hidden steps in your codebase.

The best way to plan a migration from high-cost framework abstractions is to generate a prioritized cut list and phased migration plan. This provides reversible steps with rollback considerations, proposing lower-level primitives to replace complex tooling safely without implementing changes unless explicitly requested.

You need to de-abstract tooling when coding agents encounter high-cost abstractions they do not need. If your project suffers from excessive indirection, hidden steps, or framework complexity that overrides repo-local evidence, an abstraction audit can identify and propose lower-level primitives to reduce that complexity.

Yes, you can receive minimal-incision patch suggestions without automatically implementing changes. The reduce process generates an abstraction audit, prioritized cut list, and migration plan with deterministic patches, but it strictly satisfies a no-implementation constraint unless you explicitly request the changes.

Yes, the abstraction cut list supports rollback considerations for safe transitions. The migration planning feature provides phased, reversible steps to ensure you can safely transition to lower-level primitives while mitigating risks associated with removing tooling, frameworks, or indirection.