pre-pr-check

Run pre-PR validation including tests, linting, and branch checks.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill pre-pr-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-pr-check
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/pre-pr-check
Command: npx skills add https://github.com/sburl/CrossCheck --skill pre-pr-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-PR validation that enforces quality gates before a PR is created, saving time by catching issues earlier.

Core Features & Use Cases

  • Automated tests execution and linting across languages
  • Documentation timestamp verification and update prompts
  • Branch validation and detection of uncommitted changes
  • Clear pass/fail reporting for each check to streamline reviews

Quick Start

Invoke /pre-pr-check on your feature branch to run the full pre-PR suite.

Frequently Asked Questions about pre-pr-check

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

FAQPage Schema
How do I run automated pre-PR checks before submitting a pull request?▼

Automated pre-PR checks run a validation suite on your feature branch to enforce quality gates. This process executes tests, linting, documentation timestamp verification, and branch validation to ensure code adherence before PR submission.

What is included in a pre-PR validation workflow?▼

A pre-PR validation workflow includes running automated tests, linting, documentation timestamp checks, branch validation, and uncommitted change detection. It returns a deterministic pass/fail report for each check to streamline code reviews.

Can I use pre-PR checks across different programming languages?▼

Yes, pre-PR checks apply to feature branches across multiple languages. The automated workflow runs language-agnostic validation steps including tests, linting, and branch safeguards to detect uncommitted changes.

How do pre-PR checks handle uncommitted changes and branch validation?▼

Pre-PR checks detect uncommitted changes and perform branch validation as part of their deterministic workflow. They expose hooks for these branch safeguards and return a clear pass/fail report for review before PR creation.

Why does documentation timestamp verification matter for pull requests?▼

Documentation timestamp verification ensures docs are updated alongside code changes. Pre-PR checks implement timestamp hooks that prompt for documentation updates, enforcing process adherence and saving review time by catching stale docs early.