agentleFS
Sign inStart free
owainlewisowainlewis/blueprint/skills/test/SKILL.md

test

Skill423 starsChanged 3 months agoMITView on GitHub

Proves a code change works: runs every repository check until green, then proves each acceptance criterion with tests, and with a real browser for anything visible. Use to test or verify a diff, branch, PR, URL, or user flow.

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

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 2

    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:

    Run every check the repository has: format, lint, typecheck, and tests.

    line 15
  2. Distinctive:

    If the change is visible in a browser, run the flow in Playwright.

    line 18

“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

Test

Show that each acceptance criterion passes. Reading the code is not proof.

Steps

  1. Run every check the repository has: format, lint, typecheck, and tests. The commands are in AGENTS.md, CLAUDE.md, the README, or the project's scripts. Fix what the change broke and run them all again. After three rounds on the same failure, stop and report it.
  2. List each acceptance criterion (AC-n, REQ-n, INV-n) from the ticket, word for word.
  3. Point each criterion to a test that proves it. Where none exists, write one that calls the public interface. Revert the code once to confirm the main new test fails.
  4. If the change is visible in a browser, run the flow in Playwright. Check desktop and mobile widths, keyboard use, and console errors. Save screenshots for the PR.

Return

Failures and unverified criteria first:

Criterion: <ID or exact wording>
Result: Pass / Fail / Unverified
Evidence: <command, browser flow, or screenshot>

Then each check command you ran and its result.

Fix the code, not the test. Report failures the change did not cause; leave them alone.

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