Review GitHub pull requests for correctness, security, and maintainability issues.
npx skills add https://github.com/podcodar/webapp --skill pr-review-podcodar
Please help me install this Agent Skill. Skill: pr-review Source: https://github.com/podcodar/webapp/tree/main/.agents/skills/pr-review Command: npx skills add https://github.com/podcodar/webapp --skill pr-review-podcodar
It helps teams catch issues in pull requests early by providing a structured review focused on correctness, security, maintainability, and performance.
src/ and tests, validating documentation updates, and handling large PRs by triaging with diff stats.Ask the AI to review the specified GitHub pull request URL and return a prioritized set of findings with severity labels and next-step recommendations.
High-intent search queries and answers about installing and using this skill.
To review a GitHub pull request, fetch the diff using the authenticated `gh` CLI, then evaluate changed files for correctness, security, and performance. The output is structured feedback with severity labels like [blocker] or [warning] and actionable next-step recommendations.
The best way to triage large pull requests is using diff stats to perform file-by-file evaluation across src, tests, and documentation. This method isolates critical security and correctness issues, returning a structured response with severity labels for actionable engineering feedback.
Yes, you need an authenticated GitHub `gh` CLI session to analyze a pull request diff. The review process uses `gh pr view` and `gh pr diff` commands or URL-based diff fetching to securely retrieve changes and output prioritized feedback with severity labels.
Yes, you can get automated code review feedback for src and test files before merging. The review evaluates each changed file in context, labeling findings as [blocker], [warning], or [suggestion] to validate documentation updates and catch missing test coverage or security flaws.
Automated pull request review handles secret exposure and injection risks by performing security and best-practice checks across the diff. It flags these vulnerabilities with clear severity labels and recommends next steps with rationale to prevent insecure code from merging.
dyoshikawaAnalyze GitHub pull request metadata and diffs to summarize problem backgrounds and technical solutions.
peancharoenReview git diffs and file paths for code issues with severity labels.
wesleyegbertoAutomate end-to-end verification of Spring Boot projects to gate PRs and releases.
winsorllcAutomate code review for GitHub pull requests, diffs, and files.