code-review

To get a principal-engineer code review, provide your staged file context or Git diff. The review applies domain-specific checklists and judgment tripwires to flag concrete correctness, hygiene, clarity, and security issues before commit.

An implementation-fitness gate is a quality control mechanism that evaluates modified source files. It enforces base and domain-specific checklists alongside diff-surface judgment tripwires to prevent ungrounded or out-of-scope code changes.

Yes, you can use this code review skill for frontend and infrastructure domains. It applies context-aware gating by selecting only the relevant domain checklists based on which specific files changed in your diff.

The code review handles security controls by enforcing operational coverage. It ensures that security-related changes within the modified source files have appropriate allow and deny test coverage applied during the diff analysis.

Diff-surface judgment tripwires are detection mechanisms that identify engineering judgment defects. They trigger on issues like unverified external-state claims or out-of-scope edits, preventing ungrounded modifications from passing the review gate.

Yes, the code review checks for over-elaboration in modified files. It includes a size and over-elaboration gate alongside its base and domain-specific checklists to ensure changes remain concise and appropriately scoped.