/test — Run Test Suite

Run project test suites with options for unit, integration, or end-to-end tests.

3|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/yon/agentic-dev-os --skill test-run-test-suite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /test — Run Test Suite
Source: https://github.com/yon/agentic-dev-os/tree/main/.claude/skills/test
Command: npx skills add https://github.com/yon/agentic-dev-os --skill test-run-test-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the execution of the project's test suite, providing clear and actionable results to ensure code quality and identify regressions.

Core Features & Use Cases

  • Flexible Test Execution: Run the full test suite, or specify unit, integration, or end-to-end tests.
  • Pattern Matching: Execute tests that match a specific file or pattern.
  • TDD Support: Facilitates Test-Driven Development by offering a watch mode for continuous testing.
  • Use Case: After making code changes, use this Skill to quickly verify that all tests pass and to pinpoint any new failures.

Quick Start

Run the full test suite for the project.

Frequently Asked Questions about /test — Run Test Suite

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

FAQPage Schema
How do I run specific unit or integration tests instead of the full test suite?

Run specific tests by providing file patterns to execute only matching unit, integration, or end-to-end tests instead of the full test suite. This pattern matching targets individual test files for focused execution.

Can I use watch mode for Test-Driven Development (TDD) workflows?

Yes, watch mode facilitates Test-Driven Development by enabling continuous testing. It automatically re-runs your test suite upon detecting code changes, providing immediate feedback for TDD cycles.

What reporting details are included when executing a project test suite?

Executing the project test suite reports detailed results including pass/fail counts and total duration. This reporting identifies regressions and provides actionable feedback on code quality.

What's the best way to verify code changes don't introduce regressions?

The best way to verify code changes is to execute the project's test suite immediately after modifications. This pinpoints new failures and ensures existing functionality passes without regressions.

Does this test automation tool require external dependencies to run?

No, this test automation tool requires no external dependencies to run. It directly executes your project's existing test suite configurations without needing additional setup.