run-tests

Identify and run relevant test suites, then summarize failures with likely causes.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/avav25/ai-assets --skill run-tests-avav25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/avav25/ai-assets/tree/main/.windsurf/skills/run-tests
Command: npx skills add https://github.com/avav25/ai-assets --skill run-tests-avav25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams automate the verification process by running relevant test suites and summarizing results, reducing manual testing effort and speeding feedback.

Core Features & Use Cases

  • Identify the minimal set of tests to run based on changes.
  • Execute targeted test commands and collect results.
  • Generate concise failure summaries with probable causes for faster debugging.

Quick Start

Run the run-tests skill to automatically execute the appropriate test suite for the current project and present a concise failure summary.

Frequently Asked Questions about run-tests

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

FAQPage Schema
How do I automatically run the relevant test suites for a project to verify changes?

To run test suites automatically, the skill reads TESTING.md or AGENTS.md, selects targeted test commands based on your changes, executes them, and summarizes failures with likely causes for faster debugging.

What is the best way to identify the minimal set of tests to run after a code change?

The best way to identify the minimal set of tests is using automated test selection, which reads your project configuration and targets only the specific test commands needed to validate recent changes.

How does automated test summarization help with debugging failures?

Automated test summarization helps debugging by generating concise failure summaries with probable causes, reducing manual testing effort and speeding up feedback loops during software development.

Do I need a TESTING.md or AGENTS.md file to run targeted test commands?

You need a TESTING.md or AGENTS.md file to satisfy functional requirements, as the skill reads these files to select and execute the appropriate targeted test commands for your environment.

Can I use this approach to validate changes across different stacks and environments?

Yes, you can use this approach across different stacks and environments, as it applies to software development workflows where changes require validation across multiple configurations.