testing SKILL.md skillA
testing from jorgecostamacia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jorgecostamacia/skills/testing@git:20261027.15173bdPins git:20261027.15173bd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jorgecostamacia/skills
- Path
plugins/testing/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261027.15173bd, committed Oct 27, 2026
- First version recorded
- Jul 22, 2026
- Size
- 10,423 bytes
- Repository stars
- 2
- License
- MIT
Testing principles and the pragmatic TDD loop — stack-agnostic and canon-anchored. Use when writing or reviewing tests, deciding what to test and how to name it, choosing between unit/integration/e2e, deciding whether to mock or use the real thing, judging whether coverage is enough, starting a feature test-first, or when tests are flaky, coupled or unreadable — in any language, front or back. It encodes: done means tested, the red-green-refactor loop, the test pyramid, one test file per unit…
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
# Testing & TDD (principles) Canon-anchored: sections marked **[canon]** state the standard; **[our convention]** marks deliberate positions, each with its why. Where test files live and which framework/tooling to use is each stack skill's decision. **Rules get revised, not forced: if one fights the reality of a project, question the rule.** ## Done means tested — [our convention] A use case, rule, or fix without tests **doesn't exist**. Tests are part of the change — same commit, same PR, same definition of done — never a follow-up task. The one exception: a **thin driving adapter** — one that only unpacks its input and calls a use case, with no rule of its own — may go without a unit test of its own. The composition test proves it is wired, and it is watched in production until it has behaved. Anything holding a rule is tested. ## The loop — [canon: red-green-refactor] 1. **Red** — write the failing test that states the expected behavior. Name it first: if you can't name it, you don't know what you're building yet. 2. **Green** — the simplest code that passes. No gold-plating. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hyod5v6fsiebmtio/7209043c89fa937909a415103e9253fa8066f06d9067378e9c1c7b70f8170a53.json
Then /plugin install testing@markdownregistry-hyod5v6fsiebmtio in Claude Code. It installs git:20261027.15173bd, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jorgecostamacia/skills/testing@sha256:7209043c89fa9379The line at the top of this page pins the label git:20261027.15173bd, 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_hyod5v6fsiebmtio)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in jorgecostamacia/skills/testing since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of testing from somewhere else? Ask it: where did my testing come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Jul 22, 2026 and Oct 27, 2026, about one every 24 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.15173bd latest | 2026-10-27 | 15173bd | 10,423 B | A | view · diff |
| git:20261026.fee98c8 | 2026-10-26 | fee98c8 | 9,982 B | A | view · diff |
| git:20261026.f293488 | 2026-10-26 | f293488 | 9,542 B | A | view · diff |
| git:20261026.bdadce8 | 2026-10-26 | bdadce8 | 9,274 B | A | view · diff |
| git:20260722.7129256 | 2026-07-22 | 7129256 | 8,067 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/testing/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (10423 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
jorgecostamacia/skills · 2 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hyod5v6fsiebmtio GET https://markdownregistry.com/api/v1/resolve?ref=jorgecostamacia/skills/testing GET https://markdownregistry.com/api/v1/blob/7209043c89fa937909a415103e9253fa8066f06d9067378e9c1c7b70f8170a53
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 jorgecostamacia/skills
Every file in jorgecostamacia/skills