orchestrate:review

Reviewing multiple pull requests for consistency involves validating individual PRs against commit conventions and performing cross-PR consistency validation to ensure alignment between CI workflows, pre-commit hooks, and CODEOWNERS. This process prevents integration issues by verifying that separate PRs for code, tests, and CI configurations work together harmoniously and meet project standards.

Cross-PR consistency validation in GitHub Actions CI workflows verifies alignment between different orchestration phases, ensuring pre-commit hooks match CI linting and CODEOWNERS cover created paths. It prevents integration issues by checking that separate pull requests for code, tests, and CI configurations work together harmoniously before merging.

Automate PR review for commit conventions and PR formatting by running per-PR checks against defined checklists and submitting reviews via the GitHub API. This automation validates individual PRs for commit conventions, PR format, and area-specific requirements including precommit, tests, CI, security, and replication.

Yes, you can validate CODEOWNERS and replicated skill paths across open pull requests by performing cross-PR consistency checks. This validation ensures CODEOWNERS cover created paths and verifies alignment between different orchestration phases before submitting reviews via the GitHub API.

Yes, the PR review process requires user approval before submitting reviews via the GitHub API. The system gathers all findings from per-PR checks and cross-PR consistency validation into a summary, allowing you to approve the review submission before it posts to GitHub.

A limitation of automated orchestration PR review is that it focuses strictly on defined checklists for commit conventions, PR format, and cross-PR consistency, meaning it may not catch logical bugs or domain-specific issues outside these predefined validation areas.