anti-vibe-review

You can check TDD compliance and security by running a post-implementation code review that audits recently changed modules against Anti-Vibe Coding principles. This process detects deviations in testing, architecture, and error handling to prevent quality regressions before production deployment.

Auditing a large code diff for architecture and observability issues is best handled by optionally delegating parts of the review checklist to specialized auditors. This delegation improves coverage and consistency when evaluating extensive feature changes across multiple modules.

To generate a structured code review report that classifies findings by severity, run a post-implementation audit on your target directory. The review evaluates TDD, security, and performance, producing actionable findings with severity levels and recommending relevant follow-up skills for each detected issue.

Yes, you can validate that new code behavior has real tests by performing a post-implementation review of the finished module. The audit specifically checks TDD compliance to ensure that newly implemented features are backed by actual test coverage rather than assumptions.

Post-implementation code review does detect secrets and injection vulnerabilities as part of its security audit checklist. It reviews recently changed directories to identify potential security flaws, ensuring that logging, recoverability, and data handling meet Anti-Vibe Coding standards.

You should not use an automated code audit if your changed modules lack clear architectural boundaries or if the feature lacks any preliminary implementation. The audit requires completed feature work to evaluate patterns, TDD compliance, and error handling against existing code structures.