agentleFS
Sign inStart free
steerlabssteerlabs/opensteer/.agents/skills/testing/SKILL.md

testing

Skill204 starsChanged 6 days agoMITView on GitHub

Use when diagnosing PostgreSQL integration test failures, containment or worker-contamination errors, lock-order violations or same-SHA reruns, quarantining an unresolved flaky test, selecting client attachment and Personal connection recovery checks after changing routing, catalog authority or reconnect behavior, or maintaining CI selection, shard weights, job timeouts and native-mac inputs.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bundle-dependency-prs, update-library-template and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    bundle-dependency-prs

    Fix broken dependency update PRs and aggregate the ones that work into one PR.

    Also in 7 projects that use this

  • MicrosoftSkill

    update-library-template

    Merges the latest Library.Template into this repo (at position of HEAD) and resolves conflicts.

    Also in 7 projects that use this

  • zetaloopSkill

    assign-copilot

    Assigns a GitHub issue to the Copilot coding agent, optionally specifying a custom agent. Use this when asked to assign an issue to Copilot or delegate an issue to CCA.

    Also in 3 projects that use this

  • NVIDIA-NeMoSkill

    build-and-dependency

    Dev environment setup for Megatron Bridge — container-based development, uv package management, lockfile regeneration, adding dependencies, Slurm container usage, and common build pitfalls.

    Also in 3 projects that use this

  • timmo001Skill

    changeset-scope

    Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.

    Also in 3 projects that use this

  • JetBrainsSkill

    module-dependencies

    Add or modify IntelliJ module dependencies in `.iml` files.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test infrastructure procedures.

    line 8
  2. Distinctive:

    Stop everything you start by captured PID or serial, even after a failure.

    line 14
  3. Very specific:

    Never drive the host screen: GUI and Electron checks run only in the VM (pnpm test:vm).

    line 15
  4. Distinctive:

    Never read or operate signing keys, Apple accounts or release credentials.

    line 16
  5. Distinctive:

    Never use a person's real profile, credentials, saved passwords, Messages or personal stores.

    line 17
  6. Very specific:

    Never touch the live install: ~/Library/Application Support/Opensteer, ~/Opensteer, Opensteer Beta.

    line 18
  7. Distinctive:

    Never weaken an assertion, lengthen a timeout or rerun until green.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 174 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

Testing

Test infrastructure procedures. AGENTS.md holds the rules and Testing the traps. Report commands run and checks skipped.

Safety rules

  • Devices have one owner: never take another task's simulator, emulator, USB phone or VM slot.
  • Stop everything you start by captured PID or serial, even after a failure; never kill by name.
  • Never drive the host screen: GUI and Electron checks run only in the VM (pnpm test:vm).
  • Never read or operate signing keys, Apple accounts or release credentials.
  • Never use a person's real profile, credentials, saved passwords, Messages or personal stores.
  • Never touch the live install: ~/Library/Application Support/Opensteer, ~/Opensteer, Opensteer Beta.
  • Skipped, blocked or unrun checks are unverified, never passed.
  • Never weaken an assertion, lengthen a timeout or rerun until green.

Procedures

  • Integration tests: focused runs, lock order, reruns, crash cleanup.
  • Quarantine a flaky test: recording an unresolved flake.
  • Client connections: attachment and recovery checks.
  • CI maintenance: selection, shard weights, timeouts.

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