write-tests SKILL.md skillA
write-tests from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/write-tests@git:20260303.09b1726Pins git:20260303.09b1726 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/engineer/write-tests/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.09b1726, committed Mar 3, 2026
- Size
- 3,845 bytes
- Repository stars
- 21
- License
- MIT
Write unit and integration tests. Use when the user says "write tests for this", "add test coverage", "how do I test this", "TDD", "red green refactor", "unit test this function", "test this module", "I need tests for", or has code that lacks tests - even if they don't explicitly say "write tests".
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
## Overview Based on **"Test Driven Development By Example"** by Kent Beck. Beck's core insight: tests are not a tax on development - they are the way you design. Writing the test first forces you to think about the interface before the implementation. Code written test-first tends to be more modular, more focused, and easier to change. The TDD cycle: **Red - Green - Refactor** - **Red:** Write a failing test that defines desired behavior - **Green:** Write the minimum code to make the test pass - **Refactor:** Clean up the code without changing behavior. Tests prove you haven't broken anything. ## Workflow ### Step 1: Identify what to test For a given function or module, list the behaviors to test: - The happy path (valid inputs - correct output) - Invalid inputs (what should fail gracefully) - Boundary conditions (empty, null, max, min) - Edge cases (concurrent calls, large data, unexpected types) Don't write tests for implementation details - test behavior. ### Step 2: Write the failing test first (Red) Write a test that: - Has a descriptive name: `test_<action>_<condition>_<expected_result>` - Tests one behavior per test - Has clear Arrange / Act / Assert structure …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/write-tests@sha256:d10d3b03c6077beeThe line at the top of this page pins the label git:20260303.09b1726, 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_mii3pdqgv3i3ovm7)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
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 (3845 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
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mii3pdqgv3i3ovm7 GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/write-tests GET https://markdownregistry.com/api/v1/blob/d10d3b03c6077bee648d64795cec9972974c5f6f07114971c9d4257cbd45ecb1
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 qa-aman/claude-skills
Every file in qa-aman/claude-skills