Skip to main content
Mechanical fixes and structural suggestions have different evidence requirements. The plan reports the exact ranges and refusals so you can review the change before applying it.

Mechanical fixes

Import merging refuses namespace/named combinations, mixed type-import styles, two type-only TypeScript imports, Rust use statements carrying an attribute or doc comment, side-effect imports and comments between statements. Imports in Vue and Svelte components are never removed, because the template can use a name the script check cannot see. Variables at class, module or package level are never removed. Debug removal refuses a shared-line statement, an unclosed call, arguments that could have side effects (assignments, increments, await or calls other than simple formatters), a statement that is the whole body of a braceless if, else, loop or arrow function, the last expression of a Ruby method, a removal that would leave a Go import or variable unused, and one that would leave a Python block empty. console.error is error reporting and is never eligible. Unused function deletion is a suggestion, not a mechanical fix.

Structural suggestions

The reported risk, rather than the typical risk above, governs each observation. Existing exports and changed signatures can produce changes-public-api; approval is required by default. Estimated effect is a structural estimate, not a promise that the gate will pass. Nested ranges are counted once. Reflected or framework entry points, metadata outside a proved range, ambiguous boundaries and unsupported syntax are refused. Every suggestion is subject to the language coverage table. Overview, fixes and suggestions, conventions, verification, configuration, agent integration, and language coverage.