test-impact-mapper

Map changed files to the smallest sufficient test verification set.

7|2|Updated Oct 28, 2025

Search Tags:#verification #mapping #ci #code-change #pr-review #test-selection #test-impact

Ready to run

npx skills add https://github.com/SkastVnT/AI-Assistant --skill test-impact-mapper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-impact-mapper
Source: https://github.com/SkastVnT/AI-Assistant/tree/main/.github/skills/test-impact-mapper
Command: npx skills add https://github.com/SkastVnT/AI-Assistant --skill test-impact-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map changed files to the smallest sufficient verification set to speed up PRs and CI decisions.

Core Features & Use Cases

Decision-procedure driven test mapping
File-to-test scope selection for CI and reviews
Explain why a test scope is sufficient or insufficient

Quick Start

Use this skill to determine the minimal tests to run after a code change.

Frequently Asked Questions about test-impact-mapper

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

FAQPage Schema

How do I determine the minimal set of tests to run after a code change?▼

To determine the minimal test scope after a code change, map the changed files to the smallest sufficient verification set using a structured decision procedure. This ensures you only run necessary tests for your PR review or CI workflow.

What is test impact analysis for CI workflows and PR reviews?▼

Test impact analysis for CI workflows and PR reviews is the process of mapping changed files to a minimal verification set. It applies clear scope rules to identify whether unit, integration, or manual validation is required after code changes.

How do I map changed files to specific test suites across multiple environments?▼

You can map changed files to specific test suites across multiple environments by applying file-to-test mapping and clear scope rules. This structured decision procedure selects the smallest sufficient test set for your codebase.

Can I explain why a selected test scope is sufficient for a pull request?▼

Yes, the test selection process explains why a specific test scope is sufficient or insufficient for a pull request. It uses a structured decision procedure to validate that the mapped unit, integration, or manual tests cover the code changes.

When do I need manual validation instead of automated tests during test selection?▼

You need manual validation during test selection when clear scope rules determine that unit or integration tests are insufficient for the code changes. The decision procedure evaluates the changed files to mandate manual validation when required.

Best way to minimize test scope across a codebase with multiple test suites?▼

The best way to minimize test scope across a codebase with multiple test suites is to map changed files to the smallest sufficient verification set. This structured approach avoids running unnecessary tests during PR reviews and CI workflows.