trugurpala Quality Review
Review the smallest relevant diff and load only the reference documents needed for that surface.
For user-facing product work, load references/product-engineering.md in addition to narrower references that match the changed surface.
Prioritize:
- incorrect behavior, regressions, and incomplete user workflows;
- invalid or ambiguous states;
- hidden side effects and unclear contracts;
- inconsistent domain vocabulary and weak type or API boundaries;
- data integrity, transaction, concurrency, retry, idempotency, or N+1 risks when relevant;
- authentication, authorization, validation, and other security-boundary mistakes;
- missing loading, empty, error, responsive, i18n, or accessibility behavior for product UI;
- unnecessary abstractions, requests, dependencies, or performance cost;
- missing meaningful tests, observability, or completion evidence.
Do not report formatter-owned preferences as engineering defects.
Order findings by impact and provide the smallest reasonable correction.
A review is not proof that the implementation works; hand behavioral verification to completion-proof.