skills.rest
tobilafinhangit
tobilafinhangitCOMMUNITY
Explore all skills by this author →
GitHub

pr-verification

Analyze pull request changes for regressions, destructive patterns, and breaking code.

2|Updated Feb 2, 2026
Search Tags:#code review#pull request#impact analysis#risk assessment#regression detection
One-click install
npx skills add https://github.com/tobilafinhangit/skill-master --skill pr-verification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-verification
Source: https://github.com/tobilafinhangit/skill-master/tree/main/.agent/skills/pr-verification
Command: npx skills add https://github.com/tobilafinhangit/skill-master --skill pr-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies pull requests to ensure they are safe to merge, detecting regressions, destructive patterns, and breaking changes, helping maintain codebase quality.

Core Features & Use Cases

  • Detects Destructive Changes: Identifies deletions, modifications, and renames that may lead to breaking changes.
  • Consumer Discovery: Finds all consumers of modified or deleted code to assess impact.
  • Risk Assessment: Evaluates the risk level of changes and generates a verdict.
  • Use Case: Before merging any feature branch into main, or when reviewing PRs from junior engineers.

Quick Start

Run the pr-verification skill on a pull request to verify its safety.

Frequently Asked Questions about pr-verification

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

FAQPage Schema
How do I check a pull request for regressions before merging?▼

This Skill analyzes pull request changes to detect regressions by identifying destructive modifications and breaking code, generating a risk assessment verdict to ensure codebase stability before merging.

What is impact analysis in code review and how does it find consumers?▼

Impact analysis discovers all consumers of modified or deleted code to evaluate the risk level of changes, ensuring that modifications do not introduce unexpected breaking changes to other parts of the codebase.

Can I automate risk assessment for pull requests from junior engineers?▼

You can run a dedicated verification process on pull requests from junior engineers to automatically evaluate the risk level of their changes and generate a verdict on whether the code is safe to merge.

Do I need Git to run impact analysis on my feature branch?▼

Yes, Git is required to run impact analysis on a feature branch. The verification process requires Git and specific code analysis tools to detect regressions and destructive patterns effectively.

What is the best way to detect destructive code changes before a merge?▼

The best way to detect destructive code changes is to use an automated verification process that identifies deletions, modifications, and renames, then discovers all consumers of the affected code to assess impact.

Why does regression detection fail to find all consumers of modified code?▼

Regression detection might miss consumers if the required Git environment or specific code analysis tools are not properly configured, as these are necessary to accurately trace and assess the impact of destructive changes.

Related Skills

Explore More Software Engineering Skills→
rhpdsrhpds

04-git-mcp

Connect Claude Code to the Git MCP server for repository operations.

Official
Advanced
alexandersumeralexandersumer
1

clear-merge-blockers

Identify and resolve merge blockers in code repositories with CI/CD integration.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
PrirogativusPrirogativus

security-review

Identify and mitigate security vulnerabilities in codebases via static analysis.

Community
Advanced