verify

Anti-pattern scanning identifies incomplete work indicators like TODOs, stubs, and empty error handlers within the codebase. It categorizes these findings into critical, high, medium, and low severity levels to highlight integration gaps.

The best way to check feature wiring is using a three-level verification methodology that validates file existence, confirms functions have real logic, and ensures new routes are correctly wired into the application.

Yes, you can verify code correctness by checking implementations against specific feature names. The verification process ensures the code artifacts have actual substance and are properly integrated into the broader codebase.

Automated code review for anti-patterns is limited to identifying common indicators of incomplete work like TODOs and empty error handlers. It categorizes severity levels but does not execute the application to validate runtime behavior.