testing-core

Orchestrates test runs, classifies failures by root cause, and routes fixes to responsible executors.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill testing-core-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-core
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/testing-core
Command: npx skills add https://github.com/lfuuu/claude-rules --skill testing-core-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running tests is easy, but diagnosing why they fail and deciding who should fix them is not. This Skill provides a stack-agnostic, read-only test orchestration core that runs project test commands, classifies every failure by root cause, and routes the fix to the right executor instead of patching code blindly. ## Core Features & Use Cases - Fixed diagnostic pipeline: pre-check for orphaned runs, sequential blocking execution, diagnosis, routing, and a maximum of one fix-retest iteration before escalation. - Root cause classification: every failure is categorized as code defect, test defect, environment/infrastructure issue, flaky test, or unclassifiable, with escalation instead of guessing. - Structured reporting: produces PASSED or FAILED reports with per-test failure tables, root cause localization, and recommended executors. - Use Case: A project wrapper skill imports this core and defines stack-specific test commands and a root-cause-to-executor routing table; the core then enforces the read-only contract and diagnostic discipline across unit, integration, smoke, and e2e levels. ## Quick Start Import this core from a project wrapper skill and ask the agent to run the full test suite and report any failures with root cause analysis.

Frequently Asked Questions about testing-core

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

FAQPage Schema
How do I diagnose failing tests and find the root cause?

Run the test suite through the orchestrator, which collects failed tests, tracebacks, and file:line locations, then classifies each failure as a code defect, test defect, environment issue, flaky test, or unclassifiable. Each classified failure is routed to the responsible executor.

How should flaky tests be handled in a test pipeline?

Flaky tests are recorded as a symptom with their instability pattern and delegated for stabilization. The pipeline explicitly forbids rerunning tests until they pass, since that masks the underlying race condition or ordering dependency.

Can this testing skill fix failing tests automatically?

No. The core enforces a read-only contract: it cannot edit code, tests, fixtures, or configs. It diagnoses failures and delegates fixes to the profiled executor defined in the project wrapper's routing table.

What test levels does the orchestration pipeline support?

It operates abstractly over four levels: unit, integration, smoke, and e2e. The concrete commands, runners, environments, and default modes for each level are defined by the project-specific wrapper skill.

What happens when a test failure cannot be classified?

Unclassifiable failures trigger escalation to the process owner with collected artifacts such as traces, environment logs, and failed test names. The pipeline forbids guessing a cause or assigning a random executor.