home / skills / duc01226 / easyplatform / test

test skill

safe

This skill runs tests locally using the tester subagent and analyzes the summary report to identify failures and coverage insights.

npx playbooks add skill duc01226/easyplatform --skill test

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

545 B

---
name: test
description: "[Testing] ⚡ Run tests locally and analyze the summary report."
infer: true
---

Use the `tester` subagent to run tests locally and analyze the summary report.

**IMPORTANT**: **Do not** start implementing.
**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill runs project tests locally using the tester subagent and analyzes the resulting summary report to surface failures, flaky tests, and key metrics. It helps developers quickly understand test health and pinpoint issues without running full manual triage. The skill is focused on actionable summaries and prioritized todo items for fixing test problems.

How this skill works

The skill invokes the tester subagent to execute the project's test suite in a local environment, collects the summary output, and parses metrics such as pass/fail counts, duration, and error traces. It then highlights failing tests, groups related failures, identifies flaky or slow tests, and produces a prioritized list of small tasks to address the issues. It also adds a final review task to validate fixes and improvements.

When to use it

After making code changes that may affect tests to verify regressions are caught
Before merging a pull request to get a concise test-health summary
When CI reports flaky or inconsistent test results and local reproduction is needed
During sprint retrospectives to quantify test reliability and identify hotspots
When optimizing test execution time by identifying slow tests

Best practices

Activate and use the tester subagent and any necessary analysis skills before running tests
Break down work into many small todo tasks for each failing or flaky test
Include a final review todo item to re-run tests and confirm fixes
Run tests in a clean, reproducible local environment that mirrors CI
Focus analysis on high-impact failures first: newly failing tests and frequently flaky ones

Example use cases

Run the full test suite locally after a refactor to get a prioritized list of regressions to fix
Reproduce and analyze flaky tests reported in CI to produce targeted fixes and stability tasks
Identify and document the slowest tests to plan parallelization or time improvements
Create a concise test-health report for a pull request reviewer that lists failing tests and remediation steps

FAQ

Do I need to run the tests manually before using this skill?

No. The skill uses the tester subagent to run tests locally as part of its workflow, but ensure the local environment matches CI to avoid false positives.

What kind of output does the analysis produce?

A concise summary showing pass/fail counts, failing test names with traces, flaky/slow test indicators, and a prioritized list of small todo tasks including a final review.