pr-ready

Run linting, TypeScript type-checking, unit tests, build verification, and security scans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SS2608-dev/Resilience --skill pr-ready-ss2608-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-ready
Source: https://github.com/SS2608-dev/Resilience/tree/main/.claude/skills/dev/pr-ready
Command: npx skills add https://github.com/SS2608-dev/Resilience --skill pr-ready-ss2608-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the essential checks required before submitting code for review, catching potential issues early and streamlining the pull request process.

Core Features & Use Cases

  • Automated Checks: Runs linting, type-checking, unit tests, build verification, and security audits.
  • Early Issue Detection: Identifies code style violations, type errors, failing tests, build failures, and security vulnerabilities before human review.
  • Use Case: Before pushing your changes and creating a pull request, run this Skill to confirm your code adheres to project standards and is free of critical errors, saving reviewers time and reducing back-and-forth.

Quick Start

Run the pr-ready skill to perform all pre-pull request checks.

Frequently Asked Questions about pr-ready

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

FAQPage Schema
How do I run automated checks before creating a pull request?

To run pre-pull request checks, execute this Skill to automate linting, TypeScript type-checking, unit tests, build verification, and security vulnerability scanning on your codebase before submission.

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

A pre-PR code quality checklist includes linting for style violations, TypeScript type-checking, unit test execution, build verification, and security vulnerability scanning to ensure code readiness for review.

How can I detect security vulnerabilities before submitting code for review?

To detect security vulnerabilities before code review, run this Skill to perform automated security audits and identify critical issues alongside linting and type-checking before creating your pull request.

Does this pre-PR automation tool work without external dependencies?

Yes, this pre-PR automation tool works without external dependencies, using built-in scripts and references to validate your code against project standards and identify critical issues before submission.

What's the best way to automate TypeScript type-checking and linting for a PR?

The best way to automate TypeScript type-checking and linting is running this Skill, which executes a comprehensive checklist to catch type errors and style violations before human review.

Why should I run build verification before pushing my changes?

You should run build verification before pushing changes to catch build failures early, saving reviewers time and reducing back-and-forth by ensuring your code is free of critical errors.