agentleFS
alamenaialamenai/terrae/.claude/skills/test/SKILL.md

test

Skill245 starsChanged 9 months agoMITView on GitHub

Run tests for Terrae components

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

    Run tests for Terrae components.

    line 10
  2. Distinctive:

    If the user wants to develop with live feedback:

    line 23
  3. Distinctive:

    Ask if the user wants help fixing the test or the code

    line 50

“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

Test Skill

Run tests for Terrae components.

Instructions

  1. Run All Tests

    npm run test:run

    This runs vitest in single-run mode.

  2. Run Tests in Watch Mode If the user wants to develop with live feedback:

    npm run test

    Note: This runs in watch mode and won't exit automatically.

  3. Run Specific Tests To run tests for a specific component:

    npx vitest run {component-name}

    Example: npx vitest run marker

  4. Report Results
    • Show passing/failing test counts
    • For failures, show:
      • Test name
      • Expected vs received values
      • File and line number
  5. Handle Failures If tests fail:
    • Analyze the failure reason
    • Ask if the user wants help fixing the test or the code
    • Show the relevant test file and component code
  6. Test File Location Tests are typically located at:
    • src/registry/map/__tests__/{component}.test.tsx
    • Or alongside components: {component}.test.tsx

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.