reviewing-code

Systematically evaluate code changes across security, correctness, spec alignment, performance, and maintainability.

• Evaluate code for security, correctness, performance, and spec alignment.
• Assess PRs or implementation quality against requirements.
• Apply sequential or parallel review strategies based on scope.
• Score reviews across five quality dimensions (1–100).

• Score code changes across 5 dimensions (security, correctness, spec alignment, performance, maintainability).
• Use parallel review for large PRs with specialized agents.
• Prioritize issues by severity: CRITICAL, IMPORTANT, NICE-TO-HAVE.
• Report findings with structured format including issues, recommendations, and good practices.
• Flag spec deviations requiring user approval before updating docs.
• Offer fix options: fix critical/important, review only, or suggest improvements.

1. 1.Gather context from feature specs, user stories, API contracts, and design docs.
2. 2.Apply sequential or parallel review based on PR size and scope.
3. 3.Assess each quality dimension and assign priority (CRITICAL, IMPORTANT, NICE-TO-HAVE).
4. 4.Generate a structured report with summary, findings, and recommendations.
5. 5.Flag and propose updates to specs only after user approval.