pr-review

Automating GitHub PR reviews involves fetching diffs and changed files to run code-quality checks and optionally verify against a spec.md. This skill generates a structured verdict of APPROVE, REQUEST_CHANGES, or COMMENT with a concise summary of file-level issues to post back to GitHub.

Code-quality checks in a PR diff detect bare except clauses, TODO comments without linked issues, hardcoded secrets, and missing docstrings. Analyzing the changed files surfaces these actionable issues automatically before posting a structured review back to GitHub.

Spec compliance is enforced by optionally verifying the fetched PR diff against a provided spec.md file. The skill analyzes the changes and posts a structured review back to GitHub, producing a verdict and summary of any spec violations or file-level issues.

The best way to post a structured review verdict back to a GitHub PR is to analyze the diff and changed files, run code-quality checks, and optionally verify spec compliance. This produces an APPROVE, REQUEST_CHANGES, or COMMENT verdict with a concise summary.

Automated PR review works without external dependencies or components. You run the skill on a GitHub repository with a specific PR to fetch diffs, run code-quality checks, and generate a structured verdict and summary without requiring additional setup.

Automated diff analysis streamlines merges by detecting code-quality issues and spec violations that manual reviews often miss. It fetches the PR diff, runs targeted checks for bare except clauses and hardcoded secrets, and posts a structured verdict back to GitHub to save time.