cynic-burn

To reduce code complexity and technical debt, you can analyze your codebase to identify four pathologies: orphaned files, dependency hotspots, oversized giants, and duplicates. This yields actionable verdicts like DELETE, MERGE, SPLIT, or SIMPLIFY for cleaner code.

Finding duplicated code and unimported orphaned files for refactoring involves scanning the codebase to detect similar code segments and unused modules. The process outputs clear recommendations to delete or merge these specific areas to improve maintainability.

Simplifying code and minimizing premature abstraction requires analyzing overly dependent modules and excessively large files. Instead of extracting logic, you apply a philosophy of burning complexity by splitting or merging components to systematically reduce dependencies.

Yes, this code review approach handles large files and dependency hotspots by analyzing the codebase to pinpoint excessively large files and modules with high dependency counts. It then provides targeted verdicts like SPLIT or SIMPLIFY to resolve these issues.

Automated codebase simplification recommendations should not be used when your project requires building new abstractions rather than minimizing complexity. The approach strictly adheres to a 'Don't extract, burn' philosophy, so it may not suit architectures needing extensive premature abstraction.

Cynic-burn does not require any specific dependencies to analyze code quality. It directly analyzes your project's codebase to identify orphans, hotspots, giants, and duplicates, providing actionable verdicts without needing external components.