running-tests

Run scoped per-file tests for opencode-swarm and classify failures.

437|45|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill running-tests-zaxbyhub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: running-tests
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/running-tests
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill running-tests-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of AI coding session crashes and unreliable test results caused by unbounded test fan-out, improper test runner usage, and unisolated test execution in opencode-swarm projects.

Core Features & Use Cases

  • Three-layer session guardrails: Prevents scope_exceeded errors and session kills from excessive test fan-out when using the test_runner tool.
  • Cross-platform test isolation: Provides bash and PowerShell per-file test loops to avoid mock module cache poisoning during test runs.
  • Failure triage workflow: Guides users through verifying pre-existing failures via Git worktrees, parsing CI logs, and classifying test regressions to avoid false bug reports.
  • Use Case: When you modify a single opencode-swarm agent, use this Skill to run only the relevant isolated tests without triggering a session kill, and correctly identify if any test failures existed before your changes.

Quick Start

Use the running-tests skill to safely execute the unit tests for the coder agent after making your code changes, and classify any test failures as pre-existing or new regressions.

Frequently Asked Questions about running-tests

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

FAQPage Schema
How do I prevent opencode-swarm session crashes when running tests?

Prevent opencode-swarm session crashes by using three-layer session guardrails that restrict unbounded test fan-out when executing the test runner tool. This avoids scope_exceeded errors and session kills during targeted test execution.

Why does running tests cause mock module cache poisoning in opencode-swarm?

Mock module cache poisoning occurs when tests execute without proper isolation. Cross-platform bash and PowerShell per-file test loops provide test isolation, ensuring each test runs independently without contaminating shared module caches.

How do I classify test regressions and verify pre-existing failures in opencode-swarm?

Classify test regressions by following a failure triage workflow that uses Git worktrees to verify pre-existing failures, parses CI logs, and identifies whether failures existed before your code changes to avoid false bug reports.

What's the best way to run isolated tests for a single opencode-swarm agent file?

Run isolated tests for a single opencode-swarm agent file by applying scoped test runner configuration with cross-platform per-file test loops, ensuring only relevant tests execute without triggering session instability or scope_exceeded errors.

Can I parse CI logs to identify pre-existing test failures before reporting regressions?

Parse CI logs as part of the failure triage workflow to identify pre-existing test failures before reporting regressions. This structured approach verifies whether failures existed prior to your code changes, preventing false bug reports.

Does the running-tests skill support both bash and PowerShell for test isolation?

The skill supports both bash and PowerShell for cross-platform test isolation, providing per-file test loops that prevent mock module cache poisoning and ensure reliable test execution across different operating system environments.