proving-changes SKILL.md skillA
proving-changes from ampcode/official-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ampcode/official-plugins/proving-changes@git:20261021.4f2efccPins git:20261021.4f2efcc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ampcode/official-plugins
- Path
skills/proving-changes/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261021.4f2efcc, committed Oct 21, 2026
- First version recorded
- Oct 9, 2026
- Size
- 16,780 bytes
- Repository stars
- 21
- License
- none declared
Proves that a fix or feature works end to end and breaks nothing: reproduces the failure on the unchanged code, reruns the same scenario with the change on the real stack, covers many cases and controls, and reports before and after evidence such as recordings, screenshots, logs, database state, and numbers. Use when the user asks for proof ("irrefutable proof", "prove it", "show me it works"), asks to test a change end to end, asks for before and after numbers or a demo video, or asks whether…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Proving changes Proof is evidence that convinces a reviewer who will not read the code that the change does what was claimed and breaks nothing. The reviewer decides whether to ship from the proof alone, so build it for a skeptic: every claim needs an observation that would have come out differently if the claim were false. Unit tests, type checks, and lint support proof but do not make it. A test that mocks the boundary where the bug lives passes whether or not the bug is fixed. Report them as checks, and never describe a change as verified or tested end to end on their strength alone. Proof takes as long as it takes. Spend the time to run the real scenario instead of reasoning about why it would pass. ## Workflow ### 1. List the claims and the cases Write down what must be true for the change to be correct, then the case that shows each claim. Include: - **The reported scenario**, with the reporter's exact data and conditions: the same message, repository shape, platform, browser, text size, account state, or version. …
Read the whole file at its exact version.
How to install
mdr add ampcode/official-plugins/proving-changes@sha256:9711e85186bcdd59The line at the top of this page pins the label git:20261021.4f2efcc, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mkgpexf4nuksldej)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 9, 2026 and Oct 21, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.4f2efcc latest | 2026-10-21 | 4f2efcc | 16,780 B | A | view · diff |
| git:20261017.cdc2db3 | 2026-10-17 | cdc2db3 | 15,577 B | A | view · diff |
| git:20261017.290c7f8 | 2026-10-17 | 290c7f8 | 15,613 B | A | view · diff |
| git:20261013.af3a771 | 2026-10-13 | af3a771 | 10,745 B | A | view · diff |
| git:20261009.f03ca19 | 2026-10-09 | f03ca19 | 10,653 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 (16780 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
ampcode/official-plugins · 21 stars · license none declared · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mkgpexf4nuksldej GET https://markdownregistry.com/api/v1/resolve?ref=ampcode/official-plugins/proving-changes GET https://markdownregistry.com/api/v1/blob/9711e85186bcdd592918c7bfddabbeee229bbeba3caf346ea91edfb1056a34ec
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.