pr-review

Run pre-PR quality checks for TypeScript and Next.js projects.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/SumitRajpal/nextjs-claude-architecture --skill pr-review-sumitrajpal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/SumitRajpal/nextjs-claude-architecture/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/SumitRajpal/nextjs-claude-architecture --skill pr-review-sumitrajpal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the complete pre-PR quality checklist to ensure code changes meet standards before submission.

Core Features & Use Cases

  • Enforces TypeScript correctness by running TypeScript compilation checks.
  • Validates code quality with linting across the source tree.
  • Executes test suites to verify functionality and prevent regressions.
  • Checks translations for missing keys to maintain internationalization integrity.
  • Verifies environment variable usage aligns with the declared .env.example.
  • Detects and flags debug leftovers, TODOs, and hardcoded secrets.
  • Performs a bundle size and impact check to gauge PR footprint.
  • Ensures Prisma schema changes are accompanied by corresponding migrations when applicable.

Quick Start

Run the pre-PR quality checklist before opening or merging a pull request.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate a pre-PR quality checklist for a Next.js TypeScript project?

Automate a pre-PR quality checklist by running TypeScript compilation, lint, tests, env consistency, and translation checks across your Next.js repository before opening a pull request.

What is included in a pre-PR code quality check?

A pre-PR code quality check includes TypeScript compilation, linting, test suite execution, missing translation key detection, env variable validation, and flagging debug leftovers or hardcoded secrets.

How do I check for missing translation keys before submitting a pull request?

Check for missing translation keys by running a dedicated script during your pre-PR workflow, ensuring internationalization integrity is maintained before merging code changes.

Does this pre-PR quality check work with Prisma schema changes?

Yes, the pre-PR quality check works with Prisma schema changes by detecting them and ensuring corresponding migrations are included before submission.

What environment setup is needed to run an automated lint and test workflow?

To run an automated lint and test workflow, you need a repository with TypeScript and Next.js tooling, a Bash environment, and a specific missing-keys hook script in your workflow.