pr-review

To review a pull request for code quality and architectural soundness, invoke this skill to analyze code changes, mandate research into third-party dependencies, and provide structured feedback on observations, challenges, and proposals. It identifies bugs and architectural flaws before merging.

The best way to ensure a new feature adheres to project conventions in GitHub is to use an automated code review process that checks submitted pull requests against established standards, categorizing issues and verifying correct third-party dependency usage.

Yes, you can tailor code review feedback by selecting different agent personas like Principal Architect or SDE2. This adjusts the review focus to match the specific architectural or implementation concerns relevant to that role during the pull request analysis.

Yes, the code review process mandates research into third-party dependencies to verify their correct usage and identify potential issues. This ensures new code changes integrating external libraries meet quality and architectural standards before merging.

Structured feedback improves the development workflow by categorizing specific observations, challenges, and proposals clearly. This ensures developers receive actionable, organized feedback on code quality and architectural flaws, reducing back-and-forth and accelerating the pull request merge process.

You need an automated pull request review when comprehensive analysis of architectural soundness, project convention adherence, and third-party dependency verification is required before merging, ensuring consistent quality assurance across the development workflow without manual oversight gaps.