aibom-test-impact-mapper

Map changed files to minimal pytest, npm, and Playwright test commands.

Updated Aug 27, 2026

Search Tags:#testing #pytest #npm #playwright #mapping #impact

Ready to run

npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill aibom-test-impact-mapper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aibom-test-impact-mapper
Source: https://github.com/SameerG7/synthesis-hackathon-aibom/tree/main/.codex/skills/aibom-test-impact-mapper
Command: npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill aibom-test-impact-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, pytest, npm, npx, playwright, hardhat, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Map changed files in this AI-BoM repository to the smallest reliable pytest/npm/playwright command set and optionally execute it. Use when planning verification or before finalizing any code change.

Core Features & Use Cases

Discover changed files via git
Generate candidate commands for impacted tests across overlays, completeness, IPFS, and dashboard/chain
Optionally execute the mapped commands with the provided flags to verify impacts
Reference the canonical mapping matrix in references/test-impact-map.md

Quick Start

Run this script to generate and optionally execute the minimal impact-based test commands for your changed files.

Frequently Asked Questions about aibom-test-impact-mapper

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

FAQPage Schema

How do I map git changes to minimal pytest and playwright commands?▼

To map git changes to minimal pytest and playwright commands, parse staged changes and HEAD diffs using path-based mapping rules to identify the smallest reliable test suite for impacted files. The script generates targeted verification commands across Python, Node, and frontend components.

Can I run only the impacted tests for changed files in a monorepo?▼

Yes, you can run only the impacted tests for changed files in a monorepo by using the CLI with the --from-git and --run flags. This detects changed files via git, maps them to the corresponding pytest, npm, or playwright commands, and executes the minimal test suite.

What is test impact mapping for staged git changes?▼

Test impact mapping for staged git changes is the process of identifying the minimal, impact-based test commands that correspond to modified files. It uses path-based mapping rules to generate targeted pytest, npm, and playwright verification commands instead of running the full test suite.

Does this test impact mapper support npm and hardhat components?▼

Yes, this test impact mapper supports npm and hardhat components alongside pytest and playwright. It applies path-based mapping rules to changed files in monorepos containing Python, Node, and frontend components to generate the minimal impacted test commands.

How do I execute targeted tests from a HEAD diff without running the full suite?▼

To execute targeted tests from a HEAD diff without running the full suite, use the CLI with the --from-git and --run flags. This generates candidate commands for impacted tests based on the diff and optionally executes the mapped minimal verification suite.

What's the best way to generate candidate test commands for impacted files?▼

The best way to generate candidate test commands for impacted files is to use a path-based mapping matrix that parses git changes. This approach maps changed files across overlays, IPFS, and dashboard components to the minimal pytest, npm, and playwright commands required for verification.