code-review

To perform a structured code review, apply pre-merge checklists to evaluate security, architecture, and readability. This skill enforces reference patterns and reproducible workflows to validate code quality before merging.

Multi-perspective code review systematically evaluates code changes from different angles like security and maintainability. You need it to enforce quality gates, catch edge cases, and reduce technical debt across development cycles.

To validate implementation plans, use architecture review checklists to assess design documents against project patterns and standards. This ensures architectural alignment and enforces quality gates before development begins.

Yes, you can apply a personal self-review checklist to validate your code before submitting a pull request. This enforces quality gates and reproducible workflows to catch issues early in the development cycle.

The best way to enforce quality gates is by applying structured checklists across self, peer, and architecture reviews. This disciplined framework raises code quality, catches edge cases, and reduces technical debt.

A peer review checklist should systematically cover security, architecture, maintainability, and readability. Evaluating these dimensions ensures changes meet project standards and pass enforced quality gates.