review-pr

Review pull requests for production-readiness against project conventions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the review of pull requests, ensuring code adheres to project conventions and quality standards before merging, thereby preventing production issues and maintaining code integrity.

Core Features & Use Cases

  • Automated Code Review: Checks code against a defined set of rules and conventions.
  • Production Readiness Check: Flags potential issues related to correctness, security, i18n, and adherence to project patterns.
  • Use Case: Before merging a new feature into the main branch, use this Skill to perform a comprehensive review, identifying any violations of coding standards or potential bugs.

Quick Start

Use the review-pr skill to review the pull request with number 123.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate code review for production readiness before merging a pull request?

Automated code review for production readiness analyzes pull request changes against project conventions and best practices. It verifies correctness, type safety, security, internationalization, and project-specific rules to ensure code integrity before merging into the main branch.

What specific coding standards does a pre-merge code evaluation check?

A pre-merge code evaluation checks correctness, type safety, security, internationalization, and adherence to established coding standards. It flags potential production issues by verifying code changes against project-specific rules, such as avoiding em dashes and emojis, and defined best practices.

Does automated pull request review work without external dependencies?

Automated pull request review works without external dependencies by using built-in scripts and reference components. It evaluates code changes natively to ensure quality assurance and adherence to CI/CD production readiness standards without requiring additional integration setup.

What is the best way to ensure code integrity in a CI/CD pipeline?

The best way to ensure code integrity in a CI/CD pipeline is to perform automated quality assurance checks on pull requests. This flags potential bugs, security vulnerabilities, and convention violations, preventing unverified code changes from causing production issues.

Can I check for internationalization issues during pre-merge code evaluation?

You can check for internationalization issues during pre-merge code evaluation by analyzing code changes against project conventions. The review process verifies correctness and type safety while specifically flagging i18n problems to ensure production-ready code.

Why should I use automated quality assurance checks instead of manual code review?

Automated quality assurance checks prevent production issues by consistently verifying correctness, type safety, and security against established coding standards. Unlike manual reviews, it reliably identifies convention violations and internationalization gaps before merging.