Choose proportionate verification and maintain useful tests when implementing changes, fixing bugs, or reviewing test coverage.
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 Strategy
Establish confidence proportionate to the consequences of failure, then minimize the total cost of obtaining and maintaining it. Coverage and test counts help identify gaps; they are not targets.
## Choose the verification
Identify the intended behavior and inspect existing coverage. Use repository scripts and configuration as the authority for running checks. Resolve material uncertainty about the contract before encoding an expectation.
Choose the least costly checks that exercise the behavior and the boundaries where it can fail:
- Use types and static checks for guarantees they can enforce.
- Prefer unit tests for focused logic and integration tests for collaborating code.
- Use the real environment for layout, rendering, and platform behavior.
- Exercise the changed user journey when narrower checks cannot establish that it works.
Critical behavior may warrant complementary checks at several layers. Low-risk edits do not automatically need new tests or a build. Runtime input, configuration, protocol, and schema checks remain useful when they enforce a real contract beyond static guarantees.
…
The line at the top of this page pins the label git:20261011.ef64499, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_vjxviy5cj7syld3e
GET https://markdownregistry.com/api/v1/resolve?ref=transitive-bullshit/skills/testing-strategy
GET https://markdownregistry.com/api/v1/blob/84b7ff4dc948068ab0013f3b89a6d81eb77ef46711d7f6c9aaf3f1e44d526ccb
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.
transitive-bullshit/skills · provenance/history/2026-10-11-removed/resolving-merge-conflicts/SKILL.md · Use when you need to resolve an in-progress git merge/rebase conflict.
transitive-bullshit/skills · provenance/upstream/auto-research/skill/SKILL.md · Run fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts…
transitive-bullshit/skills · provenance/upstream/better-colors/SKILL.md · Helps you build and check a color system for your project. It generates palettes, names semantic tokens, converts…
transitive-bullshit/skills · provenance/upstream/better-layout/SKILL.md · Helps with grouping, alignment, reading order, responsive structure and room for translated text, so a layout holds up…
transitive-bullshit/skills · provenance/upstream/better-typography/SKILL.md · Sets and reviews how text renders in your product, from the type scale and spacing to font features, wrapping…
transitive-bullshit/skills · provenance/upstream/better-ui/SKILL.md · Polishes the surfaces, icons and motion in your project with exact values for border radius, optical alignment…
transitive-bullshit/skills · provenance/upstream/better-writing/SKILL.md · Writes and reviews your interface copy, from labels and errors to empty states and confirmations, so it matches your…
transitive-bullshit/skills · provenance/upstream/claude/skill/SKILL.md · Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent…
transitive-bullshit/skills · provenance/upstream/codebase-design/skill/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
transitive-bullshit/skills · provenance/upstream/codex/skill/SKILL.md · Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second…
drafthq/draft · skills/testing-strategy/SKILL.md · Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill…
vodailocz/kilo-kit-mcp · skills/kilo-kit/quality/testing/SKILL.md · Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving…
transitive-bullshit/skills · skills/testing-strategy/SKILL.md · Choose testing approaches and audit test coverage. Use when the task focuses on writing or revising tests, diagnosing…