review-pr

Review pull requests across technical and business dimensions with structured findings.

6|6|Updated May 14, 2025
One-click install
npx skills add https://github.com/telekom/controlplane --skill review-pr-telekom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/telekom/controlplane/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/telekom/controlplane --skill review-pr-telekom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers assess pull requests across technical and business dimensions to ensure changes meet quality and policy standards.

Core Features & Use Cases

  • Context gathering: fetches PR metadata, diffs, commits, and CI status to build a complete review context.
  • Comprehensive evaluation: evaluates build, lint, tests, security considerations, and alignment with acceptance criteria and business requirements.
  • Actionable output: produces structured findings and a final verdict for reviewers to act on.

Quick Start

Provide a full context-aware PR review by specifying the PR or letting the system evaluate the current branch.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a GitHub pull request for both code quality and business requirements?

Review a GitHub pull request by gathering metadata, diffs, commits, and CI status, then evaluating technical aspects like build, lint, security, and error handling alongside business logic and acceptance criteria to produce a structured verdict.

What is the best way to automate PR reviews across security, lint, and coverage dimensions?

Automate PR reviews by fetching branch metadata and CI status, reading project conventions from REVIEW.md and AGENTS.md, and generating per-file context to evaluate technical dimensions like security, lint, and coverage for a prioritized action list.

Can I check if my current branch meets acceptance criteria before creating a PR?

Yes, you can evaluate the current branch by gathering its diffs and commits to check alignment with acceptance criteria, business logic, and edge cases, providing a structured evaluation with findings before submitting a PR.

Does the PR review process check API compatibility and error handling?

Yes, the PR review process evaluates API compatibility and error handling by gathering pull request metadata and diffs, assessing these technical dimensions alongside build and lint status to return a comprehensive evaluation.

How do project conventions in REVIEW.md and AGENTS.md factor into code review?

Project conventions in REVIEW.md and AGENTS.md are read during context gathering to align the code review with your established technical and business standards, ensuring the structured findings reflect your specific policy requirements.

What limitations exist when reviewing CI status and diffs for a pull request?

The review relies on the provided PR number or current branch to gather CI status and diffs, meaning it cannot evaluate changes outside that specific scope or access metadata without proper repository access configured.