pre-pr-review

Run pre-PR validation with TypeScript, Vitest, Biome, and SonarCloud checks.

3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mkatogui/universal-design-system --skill pre-pr-review-mkatogui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-pr-review
Source: https://github.com/mkatogui/universal-design-system/tree/main/plugins/universal-design-system/skills/pre-pr-review
Command: npx skills add https://github.com/mkatogui/universal-design-system --skill pre-pr-review-mkatogui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs deep review and testing of all code changes before creating a PR to catch CI failures, lint regressions, SonarCloud issues, type errors, and test failures that would block merging.

Core Features & Use Cases

  • End-to-end pre-PR validation across subsystems (types, lint, tests, builds) to reduce CI failures.
  • Diff-driven analysis to pinpoint impacted areas (packages/react, cli, tokens) and tailor validation accordingly.
  • CI-simulation and quality checks (TypeScript compilation, Vitest, SonarCloud, Biome lint) with actionable remediation guidance.
  • Comprehensive final report summarizing findings and suggested fixes when preparing for PRs.

Quick Start

Run the pre-pr-review skill on your staged changes to perform a full CI-aligned pre-PR validation.

Frequently Asked Questions about pre-pr-review

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

FAQPage Schema
How do I catch CI failures before creating a pull request?

To catch CI failures before a pull request, run a pre-PR validation that analyzes diffs and simulates CI by running TypeScript compilation, Vitest, Biome lint, and SonarCloud checks to ensure PR readiness.

What is diff-driven pre-PR validation for React and CLI projects?

Diff-driven pre-PR validation pinpoints impacted areas across React, CLI, and token projects by analyzing code changes, then tailors type checks, linting, and tests to those specific subsystems.

Can I run Vitest and Biome lint checks locally before pushing code?

Yes, you can run Vitest and Biome lint checks locally before pushing by executing an end-to-end pre-PR review that simulates the CI pipeline on your staged changes.

What do I need to simulate CI pipelines and SonarCloud checks locally?

To simulate CI pipelines and SonarCloud checks locally, you need a local repository with access to TypeScript, Vitest, Biome lint, SonarCloud, and the project build scripts.

When should I not use a pre-PR review skill?

You should not use a pre-PR review skill if your local repository lacks access to TypeScript, Vitest, Biome lint, SonarCloud, or project build scripts required to accurately simulate CI pipelines.