skills.rest
OreStudio
OreStudioOFFICIAL
Explore all skills by this author →
GitHub

code-review-pr

Identify and document quality and correctness issues in pull request changes.

25|5|Updated Jun 15, 2024
Search Tags:#security#quality#lint#code-review#pull-request#style-check
One-click install
npx skills add https://github.com/OreStudio/OreStudio --skill code-review-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-pr
Source: https://github.com/OreStudio/OreStudio/tree/main/.claude/skills/code-review-pr
Command: npx skills add https://github.com/OreStudio/OreStudio --skill code-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure pull requests meet coding standards and quality expectations by guiding and documenting the review process, reducing manual overhead and oversight gaps.

Core Features & Use Cases

  • Structured PR review: Provides a repeatable checklist that covers licensing, headers, code style, naming, and testing.
  • Deterministic guidance: Guides reviewers through a category-driven assessment of changed files and components.
  • Audit-ready findings: Generates clear findings suitable for sprint backlogs and code reviews.

Quick Start

Start by selecting a PR or commit range to review, then run through the checklist and record any findings for your backlog.

Frequently Asked Questions about code-review-pr

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

FAQPage Schema
How do I check pull request quality for code style and security issues?▼

Run a structured PR review checklist covering licensing, headers, code style, function naming, and security to identify and document quality and correctness issues across changed files, outputting structured findings for your backlog.

What is included in a comprehensive code review checklist?▼

A comprehensive code review checklist covers licensing, headers, code style, function naming, platform isolation, tests, error handling, security, and skill consistency to ensure PR changes meet coding standards and reduce oversight gaps.

Can I review specific commit ranges instead of a full pull request diff?▼

Yes, you can review specific commit ranges. The PR review process applies to diffs from main to HEAD or specific commits across multiple files and components, documenting any quality findings for the sprint backlog.

Does code-review-pr work for multi-file pull requests spanning different components?▼

Yes, PR review supports multi-file pull requests. It guides reviewers through a category-driven assessment of changed files and components, ensuring comprehensive coverage of platform isolation and skill consistency.

What is the best way to document code review findings for a sprint backlog?▼

The best way to document code review findings is to generate structured, audit-ready outputs from the PR review checklist, categorizing code style and security issues to directly populate sprint backlogs.

Related Skills

Explore More Software Engineering Skills→
CAPHTECHCAPHTECH
1

critical-code-review

Review code changes and generate structured issue lists with fix suggestions.

Official
Advanced
openshift-hyperfleetopenshift-hyperfleet
5

JIRA Ticket Triage

Validate Jira tickets for required fields and quality standards.

Official
Intermediate
webdevtodayjasonwebdevtodayjason

requesting-code-review

Review code quality with static analysis and security scans before commits.

Community
Advanced
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate