pr-impact-test

Map PR diff files to affected test suites and run targeted vitest commands.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/JiggerF/worship-ministry-app --skill pr-impact-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-impact-test
Source: https://github.com/JiggerF/worship-ministry-app/tree/main/.claude/skills/pr-impact-test
Command: npx skills add https://github.com/JiggerF/worship-ministry-app --skill pr-impact-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a PR diff, maps changed files to the exact affected test suites, runs targeted tests, and reports the full blast radius to help reviewers validate impact without executing the entire test suite.

Core Features & Use Cases

  • Map changed files to their precise test suites to identify the blast radius.
  • Run targeted vitest commands to verify only impacted tests.
  • Produce a clear blast radius report for PR reviews and pre-merge checks.
  • Use cases: when a PR is opened or updated, or you want to validate impact of recent changes before merging.

Quick Start

Provide a PR diff to initiate impact analysis and generate a blast radius report.

Frequently Asked Questions about pr-impact-test

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

FAQPage Schema
How do I run only the vitest tests affected by a PR diff?

Mapping changed files from a PR diff to exact test suites determines the blast radius. It identifies impacted tests and potential risks, compiling a structured summary to help reviewers validate impact before merge.

How do I measure the blast radius of a pull request before merging?

You need to provide a PR diff to initiate impact analysis. The system then identifies changed files, runs targeted vitest commands on impacted tests, and produces a clear blast radius report for your review.

Can I validate the impact of recent code changes without running the full test suite?

When a PR is opened or updated, this approach maps changed files to affected test suites and runs targeted vitest commands. It ensures impacted tests are verified before merge, preventing full suite execution overhead.

What is a blast radius report for CI tests and when do I need it?

Known limitations include the requirement to provide a PR diff for analysis. If changed files cannot be mapped to exact test suites, the blast radius report cannot determine the targeted vitest commands to execute.