pr-reviewer

Analyze pull requests for code quality, security, and GigLedger standards.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/kamal-haider/GigLedger --skill pr-reviewer-kamal-haider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/kamal-haider/GigLedger/tree/main/.claude/skills/pr-reviewer
Command: npx skills add https://github.com/kamal-haider/GigLedger --skill pr-reviewer-kamal-haider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often require deep contextual understanding and consistent feedback to maintain code quality and project standards. This skill provides structured guidance to reviewers, ensuring reviews are fast, focused, and aligned with GigLedger's guidelines.

Core Features & Use Cases

  • Context-aware review prompts that guide assessors to focus on scope, ticket goals, and acceptance criteria.
  • Deterministic, prioritized feedback that highlights critical issues (security, correctness, performance) and actionable next steps.
  • Use Case: A reviewer loads a PR and receives a consolidated verdict, recommended fixes, and merge-worthiness assessment aligned with the project's north star.

Quick Start

Load the PR number and repository context, then request a structured, prioritized review summary.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I streamline pull request reviews to ensure code quality and security before merging?

Streamline pull request reviews by analyzing diffs, linked tickets, and issues contextually to assess code quality, security, and merge-worthiness. This process evaluates scope and acceptance criteria to generate deterministic, prioritized feedback with actionable next steps.

What is the best way to prioritize code review feedback for critical security and performance issues?

Prioritize code review feedback using severity-based evaluation that highlights critical issues in security, correctness, and performance. This approach generates a consolidated verdict and recommended fixes, ensuring reviewers focus immediately on high-impact merge blockers.

How does contextual validation work when reviewing a pull request against project standards?

Contextual validation works by analyzing the pull request diff alongside linked tickets and issues to determine alignment with project standards. It ensures the code satisfies acceptance criteria and scope requirements before providing a structured merge-worthiness assessment.

Can I assess merge-worthiness for a pull request without manually checking the ticket scope?

Assess merge-worthiness automatically by loading the PR number and repository context into a structured review prompt. The system handles ticket scope validation and acceptance criteria matching to deliver a consolidated verdict without manual cross-referencing.

What should I do to get a structured review summary for a pull request?

Get a structured review summary by loading the PR number and repository context, then requesting the review. The system returns a deterministic, prioritized assessment containing the merge verdict, critical issue highlights, and recommended fixes aligned with project guidelines.