pr-review

Review GitHub pull request diffs for correctness, security, and conventions.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mamu7211/feirb-mailclient --skill pr-review-mamu7211
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/mamu7211/feirb-mailclient/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/mamu7211/feirb-mailclient --skill pr-review-mamu7211

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, dotnet.

What problem does it solve?

This Skill addresses the inconsistency and oversight common in manual code reviews by providing a structured, multi-dimensional analysis of pull requests.

Core Features & Use Cases

  • Comprehensive Analysis: Evaluates code against correctness, security, i18n, accessibility, and project-specific conventions.
  • Severity-Based Reporting: Categorizes findings into blockers, suggestions, nitpicks, and positive patterns for clear communication.
  • Use Case: Use this during the development lifecycle to ensure new features meet the project's strict architectural standards and test coverage requirements before a human maintainer performs the final merge.

Quick Start

Invoke the pr-review skill by providing the specific pull request number to initiate a comprehensive analysis of the changeset.

Frequently Asked Questions about pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request code reviews on GitHub for .NET projects?

Automate GitHub pull request code reviews by running build, test, and formatting verification steps using GitHub CLI and .NET SDK. This comprehensive analysis evaluates diffs against correctness, security, and project-specific conventions to deliver severity-based reports for blockers, suggestions, and nitpicks.

What does automated multi-dimensional code review check in a pull request?

Automated multi-dimensional code review checks pull request diffs against correctness, security, internationalization, accessibility, and project-specific architectural conventions. It categorizes findings into blockers, suggestions, nitpicks, and positive patterns to communicate quality issues clearly to human maintainers before merge.

Do I need GitHub CLI and .NET SDK to run automated PR reviews?

Yes, GitHub CLI and .NET SDK are required dependencies to execute automated PR reviews. The Skill invokes these tools to perform build, test, and formatting verification steps on the changeset, ensuring new features meet strict architectural standards and test coverage requirements before merge.

Can I integrate severity-based reporting into my GitHub pull request workflow?

You can integrate severity-based reporting into your GitHub pull request workflow by categorizing code review findings into blockers, suggestions, nitpicks, and positive patterns. This structured communication ensures new features meet strict architectural standards and test coverage requirements before a human maintainer merges.

What's the best way to enforce project-specific conventions during code review?

Enforce project-specific conventions during code review by analyzing pull request diffs against strict architectural standards using automated multi-dimensional analysis. The review evaluates correctness, security, i18n, and accessibility, categorizing findings by severity to ensure new features meet test coverage requirements before final merge.

When should I not use automated code review for pull requests?

Avoid automated code review for pull requests when your project lacks .NET SDK or GitHub CLI dependencies, or when changesets do not require strict architectural standard verification. The Skill requires these dependencies to execute build, test, and formatting verification steps during its comprehensive multi-dimensional analysis.