skills.rest
julianjab
julianjabCOMMUNITY
Explore all skills by this author →
GitHub

pr-review

Identify changed files and validate them against project review rules.

Updated Apr 1, 2026
Search Tags:#checklist#quality#review#diff#code#pull-request
One-click install
npx skills add https://github.com/julianjab/ia-tools --skill pr-review-julianjab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/julianjab/ia-tools/tree/main/skills/pr-review
Command: npx skills add https://github.com/julianjab/ia-tools --skill pr-review-julianjab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PR review skill identifies changed files in a branch and evaluates them against a standardized checklist to improve code quality and consistency before merging.

Core Features & Use Cases

  • Diff-driven analysis: Detect changed files in a pull request and prepare them for a standardized review.
  • Rule-driven evaluation: Load stack-specific checks from shared/stack-detection.md and rules/review.md to apply relevant standards.
  • Structured feedback: Generate a clear, prioritized report with file paths, line references, issues, severity, and actionable fixes.
  • Use Case: When reviewing a feature branch, it highlights missing tests, style violations, or security concerns to guide the merge decision.

Quick Start

Run this skill on your active branch to generate a standardized PR review against the project standards.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate code reviews against project standards?▼

To automate code reviews, this skill identifies changed files in a branch and evaluates them against a loaded checklist to provide structured feedback with file paths and actionable fixes.

How does diff-driven analysis work for pull requests?▼

Diff-driven analysis detects modified files in your active branch, loads stack-specific rules, and validates each changed file against the checklist to generate a prioritized review report.

Can I use this to check missing tests and style violations before merging?▼

Yes, you can use this skill to highlight missing tests, style violations, and security concerns by validating your branch changes against standardized project rules before merging.

Does the review output include line references and severity levels?▼

The review output includes file paths, line references, severity levels, and actionable fixes, plus a summary acknowledging good practices observed during the code review.

How are language and tooling rules determined for a code review?▼

Language and tooling rules are determined by reading shared stack detection files, which identify the stack to pull the full review checklist and apply relevant standards to changed files.

What is the best way to review a feature branch for code quality?▼

The best way to review a feature branch is running an automated skill that prepares modified files and evaluates them against rule-driven checks to guide your merge decision with structured feedback.

Related Skills

Explore More Software Engineering Skills→
7loro7loro
1

review-code

Review current branch diffs and classify issues by severity.

Community
Intermediate
ahgraberahgraber
5

code-review

Review diffs and pull requests with structured, actionable feedback.

Community
Advanced
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
korchasakorchasa

agent-tech-lead-review

Automate final pull request review and merge in an SDLC pipeline.

Community
Advanced