Run Relevant Tests

Map git-diff changes to pytest and Jest targets and execute affected tests.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill run-relevant-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Run Relevant Tests
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.cursor/skills/skill-run-relevant-tests
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill run-relevant-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and run only the test suites affected by the current change set, reducing feedback time and preserving CI integrity.

Core Features & Use Cases

  • Maps changed files to pytest and Jest targets and builds a deterministic execution plan.
  • Supports fast and deep modes to include direct tests or reverse-dependency tests.
  • Outputs a test plan and results with file:line citations and suggested fixes.

Quick Start

Run the Run Relevant Tests skill to generate a plan and execute only the tests impacted by your recent changes.

Frequently Asked Questions about Run Relevant Tests

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

FAQPage Schema
How do I run only the tests affected by my current code changes?

To run affected tests, this skill uses git diff to detect changed files and maps them to pytest and Jest targets, executing only the relevant test suites to reduce feedback time. It supports fast and deep execution modes.

How does mapping changed files to pytest and Jest targets work?

Mapping changed files to pytest and Jest targets works by applying classification rules for test locations to build a deterministic execution plan, ensuring only tests impacted by the modified API or frontend code are run.

What is the difference between fast and deep modes for running relevant tests?

Fast mode includes only direct tests for the changed files, while deep mode expands execution to include reverse-dependency tests, providing broader coverage and surfacing failures with precise file and line references.

Can I use this to run relevant tests for both frontend and API code changes?

Yes, you can use this to run relevant tests for both frontend and API code changes. It maps modified files to the appropriate Jest or pytest targets and generates a clear execution plan with cross-referenced failure results.

How do I get precise file and line references when my targeted test execution fails?

To get precise file and line references for test failures, this skill cross-references the execution results and outputs suggested fixes alongside the test plan, helping you quickly locate and resolve issues in the changed code.