review-pr

Analyze GitHub pull requests for code, dependency, CI, and test coverage.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill review-pr-thanhhuong0209
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/Thanhhuong0209/DLT-Normalization/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill review-pr-thanhhuong0209

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the comprehensive review of GitHub pull requests, ensuring code quality, identifying potential issues, and verifying documentation and test coverage.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes code diffs, checks for dependency changes, and verifies CI/CD linting and type-checking status.
  • Contextual Information Gathering: Fetches PR metadata, related issues, and comments to provide a holistic view.
  • Test and Documentation Verification: Evaluates test coverage, checks for duplication, and ensures documentation aligns with code changes.
  • Use Case: A developer can use this Skill to get a detailed, structured review of a pull request before merging, saving significant manual review time and improving code quality.

Quick Start

Use the review-pr skill to analyze the pull request with URL https://github.com/user/repo/pull/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 GitHub pull requests?

Automating code review for GitHub pull requests requires analyzing code diffs, dependency changes, and CI checks. This Skill validates test coverage and documentation updates using Python scripts and GitHub CLI to ensure code maintainability.

How do I check test coverage and documentation updates in a pull request?

Checking test coverage and documentation updates in a pull request involves evaluating code diffs against existing tests and docs. This Skill fetches PR metadata and related issues to verify alignment and detect duplication.

Do I need GitHub CLI to analyze pull request dependencies and CI checks?

Yes, GitHub CLI is required to analyze pull request dependencies and CI checks. The Skill uses GitHub CLI alongside Python scripts to fetch contextual information, verify CI/CD linting status, and validate type-checking.

What is the best way to validate CI/CD linting status before merging a GitHub pull request?

Validating CI/CD linting status before merging a GitHub pull request is best handled by analyzing CI checks and code context together. This Skill automates that process by examining dependency changes and verifying linting outcomes.

Can I fetch related issues and comments for a comprehensive GitHub pull request analysis?

Fetching related issues and comments for a comprehensive GitHub pull request analysis provides a holistic view of the changes. This Skill gathers contextual PR metadata, related issues, and comments to structure the review.