github-pr-review

Audit GitHub Pull Requests for merge readiness and code quality.

3|1|Updated Apr 12, 2026

Search Tags:#code review #pull request #github #security audit #merge readiness #metadata validation #ci checks

Ready to run

npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill github-pr-review-cogni-ai-ou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr-review
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/github-pr-review
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill github-pr-review-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

github-pr-review prevents defective or conflicting GitHub Pull Requests from getting merged by enforcing a systematic verification workflow across metadata, code changes, and CI/test readiness.

Core Features & Use Cases

PR discovery and scope alignment: Confirms intent/scope alignment, base branch drift, unresolved comment resolution, and Conventional-Commit-style title/accurate description.
Deep code inspection: Applies a code-review-driven inspection framework for hygiene, scope control (no drive-by changes), integration correctness, and overengineering/YAGNI checks.
Merge readiness verification: Validates CI status checks, test adequacy for changed vectors, and mergeability/conflict state using gh and git.

Quick Start

Load github-pr-review when you need to audit or verify a GitHub Pull Request for merge readiness and zero-defect deployment confidence.

Frequently Asked Questions about github-pr-review

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

FAQPage Schema

How do I verify a GitHub pull request is ready for merge?▼

GitHub PR review prevents defective pull requests from merging by enforcing a systematic verification workflow across metadata accuracy, code hygiene, integration correctness, and CI/test readiness.

What is included in a pull request code review and metadata validation?▼

A pull request code review includes confirming intent and scope alignment, checking base branch drift, resolving comment threads, validating Conventional-Commit titles, and inspecting diffs for hygiene and overengineering.

How do I check CI status and test coverage for changed code vectors before merging?▼

Merge readiness verification validates CI status checks, test adequacy for changed vectors, and conflict state using GitHub CLI queries and git commands to ensure zero-defect deployment confidence.

Does this PR audit workflow require GitHub CLI and git to check mergeability?▼

Yes, verifying merge readiness requires using GitHub CLI queries and git commands to validate CI status checks, branch drift, and conflict state before pull request approval.

What is the best way to prevent drive-by changes and scope creep in pull requests?▼

The best way to prevent drive-by changes is applying a code-review-driven inspection framework that enforces strict scope control, metadata accuracy, and diff-based code hygiene during the pull request audit.