vibe-redundancy-audit

You can find redundant business logic across multi-layer architectures by running a non-destructive code audit that identifies duplicated orchestration and migration remnants across command, usecase, and service boundaries, generating an evidence-based report for review.

Migration residue is stale decision-making logic that lingers across branches and commits after updates. A code audit detects this suspicious logic by analyzing multi-layer architecture paths and producing evidence-based points and rationales without modifying code.

You can audit stale code non-destructively by analyzing compatibility paths and service boundaries to identify suspicious logic. The audit generates evidence-based findings and recommendations for human review, ensuring no code is modified or deleted.

Yes, you can trace code audit findings by utilizing an automatic handoff logging system. The audit writes results to a reports directory, enabling downstream agents to access the evidence-based findings of suspicious redundant logic.

No, the redundancy audit does not automatically clean up code. It produces evidence-based points, rationales, and recommendations for duplicated orchestration across boundaries strictly for human review, maintaining a non-destructive analysis approach.

You need a redundancy audit when your multi-layer architecture accumulates duplicated decisions across command, usecase, and service boundaries, or when migration remnants linger across branches and commits, requiring evidence-based risk-assessment.