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
Test runner, generation, and coverage analysis.
**Default mode:** Module-level testing for daily development.
Full suite reserved for release verification and deep audits.
## Routes
| Subcommand | Action |
| ---------- | ------ |
| `run` | Run tests (changed modules by default) |
| `quick` | Run tests for recently changed files |
| `coverage` | Coverage analysis (module or full) |
| `gen` | Generate tests |
| `generate` | Generate tests |
| `audit` | Deep coverage audit (TestAuditWorkflow) |
| `benchmark` | Run benchmarks |
| `generate --batch` | Batch test generation |
## Usage
```bash
/testing # Ask what to do
/testing run # Run tests for changed modules
/testing run --all # Run full test suite
/testing quick # Run tests for changed files
/testing coverage # Module-level coverage
/testing coverage --full # Full codebase coverage
/testing audit # Deep coverage audit workflow
/testing gen # Generate tests
```
## Fast-Path Detection
When explicit args satisfy scoping, skip questions:
- `/testing run --all` → full suite immediately
- `/testing gen src/auth` → generate for that module
…
The line at the top of this page pins the label v2.0.0, 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_24d23vxjqzvmpzzr
GET https://markdownregistry.com/api/v1/resolve?ref=smart-ai-memory/attune-ai/testing
GET https://markdownregistry.com/api/v1/blob/feadf0ff6f4f6a335dacab16988f659895b434282fa707b64bfef6a9cb8f7cb0
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.
smart-ai-memory/attune-ai · .agents/skills/attune-hub/SKILL.md · Developer workflow hub — routes to the right skill based on what you need. Triggers on: attune, what can attune do…
smart-ai-memory/attune-ai · .agents/skills/author-feature/SKILL.md · Author a single-source feature page — a code-verified master that projects to .help kinds + docs pages, no API credits…
smart-ai-memory/attune-ai · .agents/skills/catalog/SKILL.md · Enumerate everything attune offers — every workflow, wizard, and tool, read live from the registries. Triggers on…
smart-ai-memory/attune-ai · .agents/skills/coach/SKILL.md · Progressive help for any topic. Repeat to go deeper: concept -> procedural -> reference. Triggers on: coach, learn…
davepoon/buildwithclaude · plugins/cc-best/skills/testing/SKILL.md · Testing strategies and methodologies including TDD, E2E testing, and multi-framework support
live-codes/livecodes · .agents/skills/livecodes/testing/SKILL.md · Write and run automated tests with Jest and Testing Library in the browser. Import code from script editor, use watch…
team-commonly/commonly · fleet-skills/testing/SKILL.md · Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or…
