agentleFS
Sign inStart free
databasusdatabasus/databasus/.agents/skills/testing/SKILL.md

testing

Skill9.2k starsChanged 8 days agoApache-2.0View on GitHub

Write, change, run and review tests in Databasus by the rules shared by every module. Use when writing, changing, running or reviewing tests, when fixing a bug, and when choosing which test commands a change runs.

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 171 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. Very specific:

    Run every test you wrote or changed and see it pass before you hand the work over.

    line 15
  2. Distinctive:

    Test the behavior a caller sees, at the level the module doc prefers: through the HTTP API in the backend, through exported functions and …

    line 23
  3. Very specific:

    When package tests fail because the shared test fixtures are down, such as a refused database connection or a missing container, tell the …

    line 35
  4. Distinctive:

    After a test run you stopped or that crashed, remove only what that run left behind: its containers, processes and temporary directories.

    line 39
  5. Distinctive:

    Every test you wrote or changed ran and passed, and the report says which commands ran.

    line 43
  6. Distinctive:

    No test sleeps for a fixed time to wait for a result.

    line 45
  7. Distinctive:

    Every test removes the data, files and processes it created, as the module doc describes.

    line 46

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

These rules apply in every module. The module docs add the rules of their stack: test names, the level of test they prefer, where tests live and how they clean up. Read the one for the area you work in:

  • backend/AGENTS.md, "Testing"
  • agent/verification/AGENTS.md, "Testing"

Run what you wrote

Run every test you wrote or changed and see it pass before you hand the work over. A package that compiles has not passed its tests: when you only built it or ran go vet, say so in the report instead of calling it tested.

Start a bug fix with a failing test

A bug fix starts with a test that reproduces the bug. Run it on the code before the fix and see it fail for the reason the bug describes, then fix the code and see it pass. A test that passes on the broken code proves nothing about the fix.

Test what a caller observes

Test the behavior a caller sees, at the level the module doc prefers: through the HTTP API in the backend, through exported functions and CLI commands in the verification agent. A test that pins private helpers breaks on every refactoring and still misses the contract.

Mock only external systems the test cannot run, such as a third-party API, and failures that are unsafe to reproduce, such as a full disk. A database, a container or a file system the test fixtures provide stays real.

Wait for a condition, not for time

A test that needs something to happen waits for that condition up to a limit and fails with a message when the limit passes. A fixed pause is either too short on a loaded machine or wastes time on a fast one. A negative check, such as "no notification was sent", first waits for a sign that the action was processed, so it does not pass merely because it looked too early.

Run the tests the change touched

Which tests to run, and which command never to run, is set in Several agents, one set of containers, and the commands in the table of its parent section, Development environment.

When package tests fail because the shared test fixtures are down, such as a refused database connection or a missing container, tell the user. Do not start the fixtures through just test: the developer starts the first full run.

Clean up after an interrupted run

After a test run you stopped or that crashed, remove only what that run left behind: its containers, processes and temporary directories. Never remove all containers, prune Docker or stop processes you did not start; another agent's run may be using them.

Before handing the work over

  • Every test you wrote or changed ran and passed, and the report says which commands ran.
  • A bug fix has a test that failed before the fix.
  • No test sleeps for a fixed time to wait for a result.
  • Every test removes the data, files and processes it created, as the module doc describes.
  • An OpenSpec change whose tasks add or change tests lists their commands in the "Change verification" section of its tasks.md, as the tasks rule in openspec/config.yaml describes.

Download now (ZIP)

Trending

Quiet since September.about the whole repository

Dec 2025: 0 mentionsJan 2026: 3 mentionsFeb 2026: 5 mentionsMar 2026: 4 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 2 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 2 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the databasus/databasus repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about databasus/databasus

The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 17

Talked about on GitHub, Hacker News and Bluesky (17 times).

On GitHub · 11

6 more on GitHub
  • Other versions191 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 191

    1. modelcontextprotocol/servers★ 92ksame name
    2. lobehub/lobe-chat★ 83ksame name
    3. lobehub/lobehub★ 83ksame name
    4. penpot/penpot★ 62ksame name
    5. meteor/meteor★ 45ksame name
    6. iOfficeAI/AionUi★ 34ksame name
    7. garrytan/gbrain★ 31ksame name
    8. OpenZeppelin/openzeppelin-contracts★ 27ksame name
    9. tursodatabase/turso★ 25ksame name
    10. redis/go-redis★ 22ksame name

    181 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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 6 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 6 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

      Build and dependency management for NeMo-RL. Covers Docker image building and running, uv usage, venv setup, and adding dependencies.

      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

    • NVIDIA-NeMoSkill

      linting-and-formatting

      Code style guidelines for NeMo-RL (Python and shell). Covers naming, indentation, comments, docstrings, reflection avoidance, and uv usage.

      Also in 3 projects that use this

  • In this repository19 other files it gives its agents.

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