Index of every page on this site: llms.txt
All skills
microsoft avatar

/test-discipline

@a9de923
by microsoftmicrosoft/waza1.5k stars
104
Run it yourself

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

  • 1 file
  • 1.7 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/microsoft/waza/test-discipline

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈25 tokens for metadata: the name and description. ≈389 when used: this file.

Description uses 1.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈100 characters, or 1.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at a9de923. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
domain
quality
confidence
high
source
current regression tests and retained quality incident lessons

README badge

README badge for microsoft/waza/test-discipline