Trace PR claims to code and produce a verification report.
npx skills add https://github.com/tomzx/agents --skill verify-pr-tomzx
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
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.
Issue a verification pass on a PR number to obtain a validation report and traceability findings.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
rwc9uTrack merged pull request counts per developer across a GitHub organization.
jewzaamFetch GitHub PR comments and render traceability documents as JSON and Markdown.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
ybbms777Identifies test quality gaps and false confidence risks in code diffs.
