pr-check

Automate pull request pre-checks with builds, tests, linting, and security scans.

Updated Mar 26, 2026

Search Tags:#code quality #pull request #security scanning #build verification #automated checks

Ready to run

npx skills add https://github.com/apakou/wolow --skill pr-check-apakou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-check
Source: https://github.com/apakou/wolow/tree/main/.claude/skills/pr-check
Command: npx skills add https://github.com/apakou/wolow --skill pr-check-apakou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the pre-check process for pull requests, ensuring that all necessary quality checks and compliance standards are met before merging.

Core Features & Use Cases

Build Verification: Automatically run builds and verify for zero TypeScript errors.
Test Suite Execution: Execute and validate all tests, including integration and e2e tests if present.
Linter Integration: Integrate linters to enforce code quality standards.
Security Scan: Scan for common vulnerabilities in changed files.
Compliance Check: Optionally run a compliance check or manually spot-check for accessibility issues.
Use Case: Use this Skill before submitting a PR to automatically run the entire check suite and get a detailed report on the status of build, tests, linting, security, and compliance.

Quick Start

Run the pr-check skill to ensure your pull request is ready for merge.

Frequently Asked Questions about pr-check

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

FAQPage Schema

How do I automate pull request checks for code quality and security?▼

Automating pull request checks involves running builds, tests, linters, and security scans before merging. This Skill executes that entire pre-check suite automatically to ensure code quality and compliance standards are met.

What is included in an automated pre-check process for pull requests?▼

An automated pre-check process for pull requests includes build verification, test suite execution, linter integration, security scanning for vulnerabilities, and optional compliance checks to validate code readiness before merge.

Can I use automated PR checks to verify TypeScript build errors and run tests?▼

Yes, automated PR checks can verify zero TypeScript errors during builds and execute test suites, including integration and e2e tests if present, to validate all code changes before submission.

Does the automated pre-check process run security scans on changed files?▼

Yes, the automated pre-check process runs security scans specifically targeting changed files to detect common vulnerabilities, alongside build verification, test execution, and linter integration.

How do I check code compliance and accessibility before submitting a PR?▼

You can check code compliance and accessibility before submitting a PR by running an automated check suite that optionally performs compliance checks or manually spot-checks for accessibility issues, generating a detailed status report.

What are the limitations of automating pull request pre-checks?▼

Automating pull request pre-checks relies on common build tools and security scanning libraries, meaning its effectiveness is constrained by the configurations of those underlying tools and the presence of integration or e2e tests.