agentleFS
Catherine1401Catherine1401/agent-skills/skills/test/SKILL.md

test

Skill2 starsChanged 53 days agoMITView on GitHub

After writing or changing code, guide the user through testing the changed behavior. Provide runnable mocks when the user explicitly says required APIs or backend dependencies are unavailable or unfinished.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure 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.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before finishing a coding task, provide beginner-friendly testing instructions for the changed behavior without waiting for the user to ask.

    line 6
  2. Distinctive:

    When the user explicitly says a required real API or backend dependency is unavailable or unfinished, implement runnable mock data or …

    line 8
  3. Distinctive:

    Run applicable checks and verify mock scenarios when possible.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 154 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
  • Before finishing a coding task, provide beginner-friendly testing instructions for the changed behavior without waiting for the user to ask. Inspect the project's existing run commands, test tools, and prerequisites; give exact setup and launch steps rather than assuming the user knows them.
  • Cover all cases within the changed behavior and stated requirements: successful flows, alternate branches, boundaries, validation failures, and applicable empty, loading, and error states. For each case, give concrete inputs or actions, the expected observable result, and how to reset state when needed. Distinguish checks already run by the agent from checks the user still needs to perform.
  • When the user explicitly says a required real API or backend dependency is unavailable or unfinished, implement runnable mock data or responses so the user can exercise every affected case. Do not stop at suggesting mocks or providing disconnected sample data.
  • Reuse existing mock tools, fixtures, and project conventions. Match known request and response contracts; inspect available schemas and callers, and clarify only missing contract details that materially affect testing. Mock the unavailable dependency at its boundary without changing production behavior or bypassing the code being tested.
  • Make mock scenarios deterministic and selectable so the user can trigger each outcome. Keep mock activation local to the test or development environment; explain how to enable it, select cases, reset data, and return to real services.
  • Run applicable checks and verify mock scenarios when possible. Report execution limits and identify behavior that still requires real integration testing; passing mocks does not establish that a real API or backend works.

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.