agentleFS
PMDevSolutionsPMDevSolutions/Flavian/.claude/skills/test/SKILL.md

test

Skill19 starsChanged 11 days agoMITView on GitHub

Run this repository's test suites (bats shell tests, the Node suites for the CLI wizard, the InDesign pipeline, the Claude Code configuration and hooks, the GUI, PHPUnit for a theme or plugin, the Docker-backed end-to-end suites) and report failures by name. Keywords: test, bats, node --test, phpunit, pest, test suite, e2e

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

4 rules. 0 are common, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the chosen suite(s). Keep going after a failure.

    line 26
  2. Distinctive:

    Read the output. Report every failing test by name with its first assertion message.

    line 27
  3. Distinctive:

    Never edit a test to make it pass.

    line 28
  4. Very specific:

    After the run, the post-bash-reminders.sh hooks may add a coverage or mutation-testing note.

    line 29

“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 — run the suites

Suite from $ARGUMENTS; the default is all, which runs everything except e2e (those need the Docker stack).

This repo tests shell with bats, Node with node:test, and PHP with PHPUnit. There is no pytest here; the Python test runners an older copy of this command described never applied.

SuiteCommandNeeds
batstests/bats/bin/bats tests/unit tests/figma-fse tests/canva-fse tests/validate-agent-configs.batsthe vendored submodules: git submodule update --init --recursive
initpnpm test:initNode 22+
pipelinepnpm test:pipelinepnpm install
claudepnpm test:claude (node --test tests/claude-code/*.test.mjs)Node, jq; covers the hooks, the conformance check and the doc-count check
guipnpm gui:testpnpm install
php <path>cd <path> && vendor/bin/phpunitcomposer install inside the theme or plugin (scripts/scaffold-block.sh writes a phpunit.xml.dist)
e2epnpm test:canva-e2e, pnpm test:headless-e2e, pnpm test:visual, pnpm test:lighthousedocker compose up -d wordpress db (see LOCAL-DEVELOPMENT.md)

Steps

  1. Run the chosen suite(s). Keep going after a failure.
  2. Read the output. Report every failing test by name with its first assertion message; a failure you did not cause still goes in the report.
  3. Never edit a test to make it pass. If a test is wrong, say why and propose the change.
  4. After the run, the post-bash-reminders.sh hooks may add a coverage or mutation-testing note; mention it in the report when it applies.

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.