test-suite-prioritizer

Order test execution by failure signals and tiered smoke, affected, and full runs.

1|2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/santosomar/general-secure-coding-agent-skills --skill test-suite-prioritizer-santosomar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-suite-prioritizer
Source: https://github.com/santosomar/general-secure-coding-agent-skills/tree/main/skills/testing/test-suite-prioritizer
Command: npx skills add https://github.com/santosomar/general-secure-coding-agent-skills --skill test-suite-prioritizer-santosomar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill dramatically reduces CI/CD feedback loops by intelligently ordering test execution, ensuring that tests most likely to fail due to recent code changes or historical instability are run first.

Core Features & Use Cases

  • Prioritized Test Execution: Orders tests based on signals like code coverage of changes, recent failure rates, and historical flakiness.
  • Tiered Execution Strategy: Implements smoke, affected, and full test tiers to provide rapid feedback at different stages of the development lifecycle.
  • Use Case: When a pull request causes a build to fail, this Skill ensures that the specific tests covering the modified code are executed and reported within minutes, rather than waiting for the entire, slow test suite to complete.

Quick Start

Use the test-suite-prioritizer skill to reorder the test suite based on the current git diff.

Frequently Asked Questions about test-suite-prioritizer

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

FAQPage Schema
How do I prioritize test suite execution based on code changes?

Test suite execution is prioritized by ordering tests using signals like coverage of changed code, recent failure rates, and historical flakiness. This ensures tests most likely to fail due to recent code modifications run first.

What is tiered test execution in CI/CD pipelines?

Tiered test execution implements smoke, affected, and full test tiers to provide rapid feedback at different stages of the development lifecycle. This strategy optimizes CI feedback loops by running targeted tests before full suites.

How can I reduce CI/CD feedback loops when a pull request breaks the build?

CI/CD feedback loops are reduced by running tests covering modified code within minutes rather than waiting for the entire suite. The test-suite-prioritizer reorders execution based on the current git diff to provide rapid failure detection.

Do I need coverage tools and CI history to prioritize tests effectively?

Yes, effective test prioritization requires integration with coverage tools and CI history for signal generation. These integrations provide the necessary data on code coverage of changes, recent failure rates, and historical flakiness.

Can I run only smoke and affected tests instead of the full test suite?

Yes, tiered execution supports running smoke and affected test tiers independently before the full test run. This provides rapid feedback at different development stages by executing only the most relevant tests first.