agentleFS
kapadiaskapadias/nonna/.claude/skills/test/SKILL.md

test

Skill0 starsChanged 46 days agoMITView on GitHub

Run the project's test gate — lint, type-check, tests, and coverage — then summarize failures and coverage gaps. Adapt the commands to your stack.

184 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, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 158 edited versions we read keep these.

  • 2

    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 gate for: $ARGUMENTS (if empty, the whole suite).

    line 10
  2. Distinctive:

    Never report green you did not observe: If tests failed, say so with the output.

    line 30
  3. Very specific:

    Do not mark any task done with failing tests (see .claude/rules/sync.md).

    line 32

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

!ls package.json pyproject.toml go.mod Cargo.toml Makefile 2>/dev/null

Run the gate for: $ARGUMENTS (if empty, the whole suite).

Steps

  1. Detect the toolchain from the repo (e.g. package.json, pyproject.toml, Cargo.toml, go.mod, Makefile) and run the project's gate. Typical shapes — use the one that fits:
    • JS/TS: npm run lint && npm run typecheck && npm test -- --coverage
    • Python: ruff check && mypy . && pytest --cov
    • Go: golangci-lint run && go test ./... -cover
    • Rust: cargo clippy && cargo test
    • Or make test / the repo's documented command.
  2. Run it and capture real output. Do not infer pass/fail — observe it.
  3. Summarize failures precisely: the failing test, the assertion, and the likely cause. Hand hard failures to /debug.
  4. Report coverage against the project's floor. Hold the highest bar on the survival-critical surface (money, auth, data, persistence, irreversible actions) — flag any such code lacking golden or property tests (see .claude/rules/testing.md).

Guardrails

  • Never report green you did not observe. If tests failed, say so with the output. If a step was skipped, say that.
  • Do not mark any task done with failing tests (see .claude/rules/sync.md).

Output

Pass/fail per stage, the failing-test summary, the coverage number vs. floor, and the next action.

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.