review-testing SKILL.md skillA
review-testing from posit-dev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add posit-dev/skills/review-testing@v0.1Pins v0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- posit-dev/skills
- Path
posit-dev/review-testing/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1, committed Oct 6, 2026
- First version recorded
- May 22, 2026
- Size
- 10,342 bytes
- Repository stars
- 556
- License
- MIT
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.
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
You are reviewing test code written alongside a feature implementation or bug fix. Ensure the tests are well-designed, thorough, and maintainable — not just that they pass. Tests that merely mirror implementation details create false confidence and become a maintenance burden during refactoring. ## Review Scope Identify what to review: 1. **Find changed test files** on the current branch (relative to the base branch). 2. **Find the production code** those tests cover — trace imports, function calls, and file naming conventions to map tests to their targets. 3. **Find related existing tests** for the same modules or functions that weren't changed — these may need updates or reveal gaps. Read test files first, before production code. If you can infer the feature's requirements and edge cases from the tests alone, that's a sign the tests are well-written. If you need to read the implementation to understand what the tests are doing, that's a finding worth reporting. ## What Makes a Test Valuable Weigh each test against four qualities: …
Read the whole file at its exact version.
How to install
mdr add posit-dev/skills/review-testing@sha256:f9418e6b6e32a0e6The line at the top of this page pins the label v0.1, 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_tbfcbr2df4donrgt)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 22, 2026 and Oct 6, 2026, about one every 137 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1 latest | 2026-10-06 | 0300946 | 10,342 B | A | view · diff |
| v0.1 | 2026-05-22 | 6d48d6b | 10,350 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 (10342 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
posit-dev/skills · 556 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tbfcbr2df4donrgt GET https://markdownregistry.com/api/v1/resolve?ref=posit-dev/skills/review-testing GET https://markdownregistry.com/api/v1/blob/f9418e6b6e32a0e67acb943ab70351a8a5c9cea8e6570245e443954e3d6e61ae
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.