lean-pr-review

To systematically review code, analyze pull request diffs alongside full changed file contents, classify findings into Lean waste categories, and apply severity ratings to produce a structured report with a clear merge verdict.

The best way to enforce test coverage checks before merging is to run a quality gate that analyzes changed behavior, flags missing tests, and checks for baseline breaches like dependency budget or type errors, yielding an approve or request-changes verdict.

Yes, this code review approach assigns critical, major, minor, or advisory severity ratings to each finding. It outputs complete per-finding fields including severity, file:line location, waste category, and description for consistent feedback.

To check for baseline breaches in a GitHub pull request, analyze the changed files for lines of code increases, dependency budget violations, or type errors, and flag these issues before delivering a merge-ready verdict.

Yes, you can use Lean waste classification for automated defect detection in pull requests by mapping code issues to categories like Waiting or Defects, applying severity ratings, and generating a report with an approve, request-changes, or comment verdict.