agentleFS
Sign inStart free
GitHubKnown publishergithub/squad/.copilot/skills/test-discipline/SKILL.md

test-discipline

Skill3.4k starsChanged 2 months agoMITView on GitHub

Design assertions that prove the actual contract and fail on realistic regressions

15 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

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 3

    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:

    Use this skill whenever a change affects an API, public interface, workflow contract, generated artifact, or user-observable behavior.

    line 11
  2. Distinctive:

    Update tests in the same change as an API, signature, export, or public-interface change.

    line 17
  3. Distinctive:

    Keep expected inventory arrays synchronized with the files they enumerate.

    line 26

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

Context

Use this skill whenever a change affects an API, public interface, workflow contract, generated artifact, or user-observable behavior. A passing status-only test is not evidence that the intended artifact or contract is correct.

Patterns

  • Update tests in the same change as an API, signature, export, or public-interface change.
  • Make assertions name and inspect the offending artifact, output, or configuration field—not just an exit code or broad success status.
  • Mutation-test critical gates by changing the real source or emitted artifact and proving the assertion turns red.
  • Exercise every caller path for a changed parser, normalizer, or helper; isolated unit coverage can miss the integration path that invokes it differently.
  • Reproduce working-tree-only failures locally when the contract depends on index, filesystem, line-ending, or generated-output state.
  • Keep expected inventory arrays synchronized with the files they enumerate.

Examples

A workflow-compilation test mutates the source workflow, compiles it, and inspects the emitted safe-output contract. A repair-script test constructs the actual index/blob/worktree state that the repair routine must handle instead of a simplified fixture.

Anti-Patterns

  • Calling a test sufficient because it observes only a successful process exit
  • Mutating a hand-built fixture instead of the source or artifact protected by the gate
  • Testing a helper while omitting production callers
  • Treating a local checkout defect as something CI alone can validate

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