review-pr

Review staged and unstaged branch changes against frontend and backend standards.

Updated Mar 6, 2026

Search Tags:#git #frontend #backend #quality #review #code-review #tests

Ready to run

npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill review-pr-nand1234

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/nand1234/Agentic-workflow-builder/tree/main/ai-dev-worflow/.claude/skills/review-pr
Command: npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill review-pr-nand1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review all changes in this branch to ensure frontend and backend standards are met.

Core Features & Use Cases

Automated diff analysis: Detects changed files and classifies them as frontend or backend.
Standards checks: Verifies code against project conventions, docs, and test coverage.
Structured feedback: Produces a clear report with must-fix issues, suggestions, and a final verdict.

Quick Start

Review the current branch before pushing or creating a PR to get a structured feedback report.

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I automate code review for staged and unstaged changes before creating a PR?▼

To automate pre-PR code review, you can run a review process that diffs HEAD and cached changes, classifies modified files, and evaluates them against project standards. This generates a structured report with must-fix issues and a final verdict.

How does a pre-PR code review check frontend and backend standards?▼

A pre-PR code review checks frontend and backend standards by reading project specification files like frontend.md and backend.md. It diffs branch changes against these conventions to ensure code quality and test coverage requirements are met.

Can I review both frontend and backend code changes in a single pass?▼

Yes, you can review both frontend and backend code changes in a single pass. The review process detects changed files, automatically classifies them by stack, and evaluates them together against frontend and backend standards before you push.

What is the best way to verify test coverage and code quality before pushing a branch?▼

The best way to verify test coverage and code quality before pushing is to perform an automated pre-PR review. It evaluates your branch diff against project standards and test coverage rules, returning a structured feedback report with a final verdict.

What does a structured pre-PR code review report include?▼

A structured pre-PR code review report includes a classification of modified files, an evaluation of code quality against project standards, must-fix issues, suggestions, and a final verdict on whether the branch is ready for a PR.