check-tests

Automates running tests, tracking coverage history, and detecting regressions for software projects.

5|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mataeil/OODA-loop --skill check-tests-mataeil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-tests
Source: https://github.com/mataeil/OODA-loop/tree/main/skills/check-tests
Command: npx skills add https://github.com/mataeil/OODA-loop --skill check-tests-mataeil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running a project’s test suite and tracking its quality over time can be tedious and error-prone. This skill automates test execution, gathers results, and surfaces regressions to keep you informed without manual checks.

Core Features & Use Cases

  • Execute the configured test command to run the project’s tests and collect pass/fail information.
  • Track test coverage history by reading and updating agent/state/test_coverage.json.
  • Detect regressions and generate concise alerts to help teams respond quickly in CI or local development.

Quick Start

Run the test suite using the configured test_command and monitor agent/state/test_coverage.json for results.

Frequently Asked Questions about check-tests

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

FAQPage Schema
How do I automate running tests and track coverage history in CI?

You can automate running tests and track coverage by executing a configured test command and writing results to agent/state/test_coverage.json, which maintains ongoing coverage history for local CI and monorepos.

How do I spot test regressions during ongoing feature development?

You spot regressions by running the automated test suite, which compares current pass/fail results against historical coverage data and surfaces regression alerts to help you respond quickly during feature work.

Can I configure a custom test command and timeout for a monorepo?

Yes, you can configure a custom test_command and test_timeout_seconds to support monorepos and local CI environments where test commands vary across different project components.

What is the best way to monitor test coverage trends over time?

The best way to monitor test coverage trends is by reading and updating agent/state/test_coverage.json, which stores coverage history and produces status updates for ongoing tracking.

Does automated test execution work without external dependencies?

Yes, automated test execution works without external dependencies, relying solely on configured test_command and test_timeout_seconds parameters to run tests and collect pass/fail information.