regression-testing SKILL.md skillA
regression-testing from nahid-sparktales/agent-dispatcher is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nahid-sparktales/agent-dispatcher/regression-testing@git:20260921.94f508dPins git:20260921.94f508d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nahid-sparktales/agent-dispatcher
- Path
skills/quality/regression-testing/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260921.94f508d, committed Sep 21, 2026
- First version recorded
- Sep 19, 2026
- Size
- 7,228 bytes
- Repository stars
- 58
- License
- MIT
Turn a fixed bug into a test that fails on the old code and passes on the new one. Assert behavior at the cheapest useful level and compare old behavior without reverting unrelated work or leaving scratch files. Use after a fix or when recurring defects lack coverage; not for a new feature's test strategy or an environmental/cosmetic failure.
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
# Regression testing A test written after the fix, run once, green, proves only that the code currently passes it. It becomes a regression test at the moment you watch it fail against the old code — until then it may be asserting nothing at all. ## When this fires - A bug has been fixed and the fix is about to be reported as done. - A defect has recurred, so the previous fix had no test or the test did not cover the real case. - A test exists for a fix but was never observed failing without it. It does not fire for new-feature coverage, for test strategy, or before the cause is understood — a test pinning a symptom you cannot explain pins the wrong thing. ## Procedure 1. **Restate the defect as a behavioural assertion.** Given this input and this state, the system should do this. If that sentence cannot be written, the diagnosis is not finished (`systematic-debugging`), and the test will end up asserting the implementation instead. 2. **Decide whether a test is the right tool at all.** See *When not to write one* below. Write nothing rather than something that will be deleted as noise in a month. …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/regression-testing@sha256:3f1d04050d8bb173The line at the top of this page pins the label git:20260921.94f508d, 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_ssso7nmrxsp5un4x)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 19, 2026 and Sep 21, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.94f508d latest | 2026-09-21 | 94f508d | 7,228 B | A | view · diff |
| git:20260920.a709161 | 2026-09-20 | a709161 | 7,238 B | A | view · diff |
| git:20260919.a0d4f55 | 2026-09-19 | a0d4f55 | 6,827 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 (7228 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
nahid-sparktales/agent-dispatcher · 58 stars · license MIT · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ssso7nmrxsp5un4x GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/regression-testing GET https://markdownregistry.com/api/v1/blob/3f1d04050d8bb17304c65f8e0fae8697d51011f4287fbc494422d06176c52f31
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.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher