crew-review

To review staged git changes for operational risks, you can analyze the git diff content to detect defects and missing tests before shipping. This yields severity-ordered findings with specific file and line references to highlight critical issues.

An adversarial code review of a working tree diff systematically analyzes code changes to uncover concrete defects, missing tests, and operational hazards before production. It prioritizes risk-first reporting by surfacing severity-ordered findings over style issues.

Yes, you can check test coverage gaps using git diff analysis by evaluating staged changes or working tree modifications. The review identifies test gaps and reports open questions alongside severity-ordered findings to close coverage holes.

Yes, this code review approach works with specific paths or PR base refs by parsing the scope of your git status. It analyzes the relevant diff content for the specified context and produces severity-ordered defect findings with file references.

The best way to find production bugs in working tree code changes is performing a diff-focused defect detection analysis. This method targets concrete regressions and operational hazards, outputting severity-ordered findings with open questions to resolve before shipping.

You should not use automated diff analysis for code review when you need style enforcement or formatting fixes, as this approach prioritizes concrete defects, regressions, and operational risks over stylistic code issues.