agentleFS
Sign inStart free
ZaxbyHubZaxbyHub/opencode-swarm/.agents/skills/running-tests/SKILL.md

running-tests

Skill517 starsChanged 3 days agoMITView on GitHub

Codex adapter for safely executing opencode-swarm tests. Use whenever Codex needs to run focused tests, per-file isolation loops, CI-equivalent validation, test-impact checks, or diagnose failing/truncated test output without stalling the session.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this adapter when executing tests in opencode-swarm.

    line 10
  2. Very specific:

    Use the available shell execution tool for bun --smol test and PowerShell/bash loops.

    line 19
  3. Very specific:

    Prefer rg and repo scripts to rediscover exact commands from source.

    line 20
  4. Very specific:

    Do not use broad OpenCode test_runner scopes for repo validation.

    line 22
  5. Distinctive:

    Default rule: one source file or one explicit test file can be targeted narrowly.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Running Tests

Use this adapter when executing tests in opencode-swarm. For writing tests, load $writing-tests instead.

Read, in order:

  1. AGENTS.md
  2. .opencode/skills/running-tests/SKILL.md

Codex-specific execution notes:

  • Use the available shell execution tool for bun --smol test and PowerShell/bash loops.
  • Prefer rg and repo scripts to rediscover exact commands from source.
  • Capture long output to a temp file when needed and report the important tail or failure lines.
  • Do not use broad OpenCode test_runner scopes for repo validation.
  • On Windows, if Bun reports EPERM after a forced dependency refresh, rerun the same focused command with approved/elevated access before treating it as a test failure.

Default rule: one source file or one explicit test file can be targeted narrowly; multiple files or directories should use shell loops or the documented tier commands.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free