drive-pr-local-review

To generate local code review artifacts for a git branch, use an automation skill to compare the current branch against its base. This produces structured review documents including system design and code review files locally.

A comprehensive pull request review typically requires a canonical specification, a system design review, a detailed code review, and a walkthrough document to ensure all aspects of the change are considered before merging.

You can automate PR review documentation by running a skill that extracts expectations from canonical specs or PR descriptions and generates markdown review files. This ensures comprehensive and consistent feedback for your development workflow.

Yes, you can generate a system design review locally before merging a pull request. The automation creates a system-design-review.md file by comparing the current branch against its base to analyze the structural changes.

The best way to establish review expectations for a code branch is to derive them from canonical specs, PR descriptions, or inferred requirements. This ensures the generated code review aligns with the intended changes.

You do not strictly need an existing canonical specification to generate a walkthrough document. The automation will establish expectations from PR descriptions or inferred requirements if a canonical spec is not present.