km:quality-review

To review a git diff, run a checklist-based analysis against ISO/IEC 25010 characteristics to detect security, maintainability, and reliability issues. This process maps uncommitted file changes to standard quality metrics and generates a structured report with categorized findings.

Checking uncommitted changes against ISO/IEC 25010 involves evaluating the git diff across nine quality characteristics like performance and reliability. The review outputs a summary with PASS, WARN, FAIL, or SKIP statuses per characteristic, backed by diff evidence.

Checklist-driven code review for feature branch diffs works by applying a prioritized quality checklist to decide the review scope, then consulting reference files for anti-patterns. It identifies ownership gaps, N+1 patterns, and unsafe input handling before merging.

Yes, you can use automated quality reviews to detect regression risks before merging by analyzing uncommitted changes. The review evaluates reliability and security metrics, producing categorized findings from CRITICAL to LOW to support commit gating decisions.

Code quality review provides traceable evidence for engineering decisions by mapping categorized findings directly back to specific git diff lines. This ensures that PASS, WARN, and FAIL evaluations are justified by reference-backed guidance and anti-patterns.

You should avoid using ISO/IEC 25010 for code review when evaluating purely stylistic or formatting changes, as the checklist focuses on functional characteristics like security, reliability, and performance rather than code style enforcement.