requesting-code-review

Validating code changes before a git merge involves reviewing completed software updates against requirements to identify implementation issues. The process uses structured reviewer context and git commit ranges to classify issues by severity and provide actionable feedback.

A structured code review for software development is a validation process that evaluates implementation issues before merging. It applies review criteria covering requirements alignment, architecture, testing, security, and production readiness to ensure changes do not cascade flaws into production.

Requesting a code review using a subagent workflow involves dispatching a dedicated reviewer subagent with precise implementation context. This avoids relying on conversation history and instead provides structured reviewer context and git commit ranges for accurate evaluation.

You need to run a pre-merge validation checkpoint when finishing a major feature, completing a refactoring task, or finalizing a development task. This checkpoint catches implementation issues before changes are merged or extended into further development.

Yes, the code review process works with standard git commit ranges to evaluate completed changes. It requires specifying the commit range and structured reviewer context to accurately identify issues and assess production readiness.