agentleFS
int2t05int2t05/engineering-skills/skills/06-test/test-generation/SKILL.md

test-generation

Skill3 starsChanged 29 days agoMITView on GitHub

Add meaningful tests for existing behavior with actual project tooling. Triggers on "generate tests", "生成测试".

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 4

    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:

    Add meaningful tests for existing behavior with actual project tooling.

    line 10
  2. Distinctive:

    Read the contract, public interface and tests.

    line 16
  3. Distinctive:

    Use project layout, isolated data and independently derived expectations.

    line 20
  4. Distinctive:

    Run cases and affected regressions and verify they detect the intended defect or missing behavior.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 8 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 Generation (Language-Agnostic)

When to use

  • Add meaningful tests for existing behavior with actual project tooling.

Not for: tdd for test-first changes; e2e-testing for journeys.

Steps

  1. Read the contract, public interface and tests; identify genuine gaps.
  2. Build a compact normal, boundary, error and relevant state or concurrency matrix.
  3. Use project layout, isolated data and independently derived expectations; label substitutes separately from integration.
  4. Run cases and affected regressions and verify they detect the intended defect or missing behavior.

Verify

  • Tests exercise actual behavior reproducibly and detect meaningful failures rather than mirroring implementation.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • clean-code.md — clean code principles for test quality
  • references/language-patterns.md — per-language Test Framework | Assertion Style | Mock Library mapping

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.