verify-pr

Trace PR claims to code and produce a verification report.

5|Updated Jul 25, 2025

Search Tags:#automation #review #code-quality #traceability #static-analysis #verify #pull-request

Ready to run

npx skills add https://github.com/tomzx/agents --skill verify-pr-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-pr
Source: https://github.com/tomzx/agents/tree/main/skills/verify-pr
Command: npx skills add https://github.com/tomzx/agents --skill verify-pr-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often require rigorous quality checks beyond runtime validations. This skill performs a static inspection of a pull request to ensure code quality, architectural alignment, and precise claim-to-code traceability without building or executing.

Core Features & Use Cases

Claim-to-code traceability: map each PR claim to the specific files, functions, and modules touched.
Quality and architecture checks: detect dead code, missing tests, and architectural drifts against the PR description.
Automation-ready verification: generate a structured verification report for PRs, comments, and audits.

Quick Start

Issue a verification pass on a PR number to obtain a validation report and traceability findings.

Frequently Asked Questions about verify-pr

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

FAQPage Schema

How do I trace pull request claims to specific code changes?▼

Static PR verification maps each pull request claim to the specific files, functions, and modules touched. This claim-to-code traceability validates that PR descriptions accurately reflect modified code without requiring a build or execution.

What is static pull request verification and when do I need it?▼

Static pull request verification is a formal review process that checks code quality, architecture alignment, and claim-to-code traceability without executing code. You need it after a PR passes runtime validation but before a formal review to detect dead code and architectural drifts.

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

You automate code quality checks by issuing a verification pass on a PR number to perform static inspection. The process detects dead code, missing tests, and architectural drifts against the PR description, generating a structured verification report for comments and audits.

Does static PR verification work without building or executing the code?▼

Yes, static PR verification performs a formal inspection to ensure code quality and architecture alignment without building or executing. It traces claims to code and checks for missing tests and dead code through static analysis rather than runtime validation.

Best way to detect architectural drift and dead code in a pull request?▼

The best way to detect architectural drift and dead code is performing static inspection against the PR description. This verification process checks for dead code, missing tests, and architectural alignment while mapping claims to modified files and functions.

What limitations should I expect with static PR verification?▼

Static PR verification is limited to formal code inspection without building or executing, so it does not replace runtime validation. It applies exclusively to pull requests that have already passed runtime validation and are ready for a formal verification review.