code-review

Review a pull request by applying a structured checklist to evaluate code correctness, security, error handling, and maintainability. This process analyzes git diffs to surface TODO markers, console logs, and potential breaking changes before merging.

Check staged commits for quality by running automated git diff analysis to identify changed files and evaluate edge cases. This verifies adherence to project coding standards and highlights potential maintainability issues.

You can run your test suite during a code review by using an integrated test verification step. This executes the project's tests and highlights recent failures to ensure robust code before merging.

Automate code review for a feature branch by applying a severity-rated checklist to the git changes. This systematically surfaces critical security issues, evaluates performance, and ensures required tests are present.

This code review process requires access to the git repository, test suite, and project coding standards. These inputs allow the review to analyze staged commits or completed feature branches effectively.

A code review might miss breaking changes if it lacks automated git diff analysis. Applying a structured checklist detects changed files, TODO markers, and potential breaking changes to prevent technical debt.