agentleFS
Sign inStart free
proffesor-for-testingproffesor-for-testing/agentic-qe/.agents/skills/aqe-test-change/SKILL.md

aqe-test-change

Skill515 starsChanged 22 days agoMITView on GitHub

Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Read AGENTS.md, the changed code, nearby tests, and relevant public interfaces.

    line 8
  2. Distinctive:

    Add tests in this order:

    line 13
  3. Distinctive:

    Keep tests deterministic. Do not hide failures with retries, skips, weakened assertions, fabricated fixtures, or mocks of the behavior …

    line 17
  4. Distinctive:

    Run the narrowest matching Vitest target first.

    line 19
  5. Very specific:

    Never modify or reset .agentic-qe/memory.db.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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 an AQE Change

  1. Read AGENTS.md, the changed code, nearby tests, and relevant public interfaces.
  2. Reproduce a reported defect with the exact scenario before changing code.
  3. Identify the affected QE specialty from references/test-specialties.md.
  4. Add tests in this order:
    • durable boundary contracts, invariants, or properties;
    • integration behavior across affected components;
    • focused unit examples needed for the red-green loop.
  5. Keep tests deterministic. Do not hide failures with retries, skips, weakened assertions, fabricated fixtures, or mocks of the behavior under test.
  6. Run the narrowest matching Vitest target first. Expand to typecheck, build, agent/skill parity, MCP integration, or full CI checks in proportion to the changed surface.
  7. For capabilities exposed through both CLI and MCP, verify both paths.
  8. Report commands, pass/fail counts, limitations, and untested external dependencies.

Never modify or reset .agentic-qe/memory.db. Use a copy for any database test.

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