verify-pr

Run typecheck, lint, build, tests, and CI checks before merging pull requests.

97|4|Updated Mar 25, 2026

Search Tags:#merge #docs #pr #quality-check #lint #ci #tests

Ready to run

npx skills add https://github.com/go-to-k/cdkd --skill verify-pr-go-to-k

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-pr
Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/verify-pr
Command: npx skills add https://github.com/go-to-k/cdkd --skill verify-pr-go-to-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR readiness is a multi-faceted challenge: it requires validating code quality, ensuring tests pass, confirming CI status, and verifying documentation consistency before merging. This Skill automates a comprehensive verification workflow to ensure that a pull request is safe to merge and aligns with project governance.

Core Features & Use Cases

Runs typecheck, lint, and build to catch issues early in PRs.
Executes unit and integration tests and reports results.
Verifies documentation consistency and state cleanliness, and checks for stale references or leftover resources.
Applies gating and marker checks to ensure CI is green and gates allow merge when safe.

Quick Start

Run the verify-pr skill against the PR to perform all checks and ensure the PR is ready to merge.

Frequently Asked Questions about verify-pr

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

FAQPage Schema

How do I automate PR readiness checks before merging to main?▼

To automate PR readiness checks before merging to main, run a comprehensive workflow that validates typecheck, lint, build, unit tests, and CI status. This ensures no regressions reach the main branch by enforcing quality and merge gate markers.

What is a PR quality-check workflow for code changes and documentation updates?▼

A PR quality-check workflow is an automated verification process that runs front-end checks, executes tests, and validates documentation consistency. It ensures code changes and docs remain in sync while preventing regressions from reaching main.

Can I verify documentation consistency and check for stale references in a pull request?▼

Yes, you can verify documentation consistency by checking for stale references and leftover resources during the PR verification process. The workflow validates that documentation remains in sync with code changes and confirms state cleanliness before merge.

How do I ensure CI is green and merge gates allow a safe merge?▼

To ensure CI is green and merge gates allow a safe merge, apply gating and marker checks that validate CI status and confirm all tests pass. This automated guardrail verifies the PR is safe to merge and aligns with project governance.

Does the PR verification process run typecheck, lint, and build checks together?▼

Yes, the PR verification process runs typecheck, lint, and build checks together to catch issues early. It executes these front-end checks alongside unit and integration tests, reporting results to ensure comprehensive readiness before merge.