verification-discipline skillA
verification-discipline is agent-read markdown (skill) from microsoft/amplifier-bundle-skills: Use when verifying that completed work actually works. Auto-surface during /verify mode, post-implementation review, or before claiming a task is done. Teaches testing outcomes vs implementation, the unit/integration/smoke gradient, and what "done" actually means..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Verification Discipline ## The Principle Unit tests verify that **code-as-written behaves as-written**. Smoke and integration tests verify that **the system achieves the intended outcome**. Those are different questions. You need both. "All unit tests pass" is necessary. It is rarely sufficient. A finding from the field: four consecutive integration-blocking bugs, all of which passed unit tests, all of which would have been caught by a five-minute smoke test on a fresh environment. The bugs were not exotic — they were the cost of declaring "done" too early. ## The Four Failure Modes 1. **Tests written from the implementation outward miss scenarios the code doesn't anticipate.** The engineer writes code, then writes tests that exercise the code as written. The tests ask "does this code do what I wrote it to do?" They don't ask "what scenarios does the system need to handle?" 2. **Mocks verify shape, not behavior.** A mocked dependency returns the value you told it to return. That tells you nothing about whether the real dependency would have behaved that way. 3. **Tests in isolation miss integration boundaries.** Component A passes. …
Read the whole file at its exact version.
How to install
mdr add microsoft/amplifier-bundle-skills/verification-discipline@git:20260830.e465f5emdr add microsoft/amplifier-bundle-skills/verification-discipline@sha256:38d63c801990b519Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pmt2yunrjxfnsfag)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260830.e465f5e latest | 2026-08-30 | e465f5e | 6,072 B | A | view · diff |
| git:20260519.d95880b | 2026-05-19 | d95880b | 6,091 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6072 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
microsoft/amplifier-bundle-skills · 12 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pmt2yunrjxfnsfag GET https://markdownregistry.com/api/v1/resolve?ref=microsoft/amplifier-bundle-skills/verification-discipline GET https://markdownregistry.com/api/v1/blob/38d63c801990b5191d358008cb866a5e881f5d75999e6fcc08e9fb5ae5b25071
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from microsoft/amplifier-bundle-skills
Every file in microsoft/amplifier-bundle-skills