qa-reviewer

To prevent regressions, apply a checklist-driven QA review on changed files to validate happy paths, error handling, edge cases, type-safety, and accessibility before merging. This enforces explicit checks and assesses regression risk to ensure functional correctness.

A checklist-driven code review covers happy path execution, error handling, edge-case coverage, strong TypeScript type-safety, and accessibility considerations. It examines only changed files and reports findings with severity levels like CRITICAL, SUGGESTION, or OK.

Perform a pre-merge QA review by reading the task file, examining only the changed files, and validating behavior and error handling across diverse data paths. Capture reviewer notes back into the task file to communicate risks and required fixes.

Yes, this regression testing approach explicitly validates edge cases and enforces strong type-safety. It applies explicit checks across diverse tasks and data paths to identify potential regressions and ensure robust functional correctness.

The best way to document findings is to report them with severity levels (CRITICAL, SUGGESTION, OK) and capture reviewer notes directly back into the task file. This communicates risks and required fixes effectively for pre-merge validation.

Use a checklist-driven QA review during code reviews, feature testing, and pre-merge validation when you need to enforce explicit checks for edge cases, type-safety, and accessibility that standard testing might miss.