pr-ready

Run tests, type checks, and Prettier formatting on changed packages.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/rosinbum/usopc-athlete-support-agent --skill pr-ready-rosinbum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-ready
Source: https://github.com/rosinbum/usopc-athlete-support-agent/tree/main/.claude/skills/pr-ready
Command: npx skills add https://github.com/rosinbum/usopc-athlete-support-agent --skill pr-ready-rosinbum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the pre-pull request quality checks, ensuring code adheres to standards before submission and saving valuable review time.

Core Features & Use Cases

  • Automated Testing: Runs unit tests for changed packages.
  • Type Checking: Verifies TypeScript type correctness.
  • Code Formatting: Ensures consistent code style with Prettier.
  • Use Case: Before pushing your feature branch, run this skill to catch any test failures, type errors, or formatting issues, allowing you to fix them locally and submit a clean PR.

Quick Start

Run the pr-ready skill to check the quality of your code before creating a pull request.

Frequently Asked Questions about pr-ready

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

FAQPage Schema
How do I run pre-PR quality checks for TypeScript and Prettier?

Pre-PR quality checks validate code by executing unit tests, TypeScript type checks, and Prettier formatting across changed packages. This identifies specific failures and provides actionable commands for remediation before pull request submission.

What is the best way to automate code review checks before creating a pull request?

Automating code review checks before a pull request involves running a quality gate to verify test pass rates, type correctness, and formatting adherence. This enforces project conventions locally and prevents integration issues from reaching remote branches.

Can I run tests and type checks only on changed packages instead of the whole project?

Yes, pre-PR validation targets changed packages specifically, executing tests and type checks only on affected code. This saves review time by isolating failures to modified files and reporting precise commands to fix integration issues.

Why does my pull request fail the quality gate when code formatting is inconsistent?

A pull request fails the quality gate when code style deviates from project conventions. The pre-PR check runs Prettier to detect formatting issues, reporting specific failures with actionable remediation commands to fix style inconsistencies locally.

Does pre-PR validation work without external dependencies or components?

Pre-PR validation operates independently without external dependencies or components. It executes tests, type checks, and formatting checks natively against your project conventions to ensure code quality before pull request integration.