testing-codegen skillA
testing-codegen is agent-read markdown (skill) from modem-dev/ossrules: Use this skill when selecting or running Biome test fixtures, quick tests, `insta` snapshot workflows, expectation comments, orphan checks, or required code generators. Do not use for subsystem implementation design..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Testing and Code Generation Choose the narrowest test that exercises the changed behavior, then broaden only when shared infrastructure or integration risk justifies it. ## Test Selection | Change | Start with | | --- | --- | | Lint rule | `just test-lintrule <ruleName>` | | One crate | `cargo test -p <crate>` or the crate's focused test target | | Parser or formatter investigation | `just qt <package>` | | CLI migration | focused `biome_cli` migration tests | | Documentation code | `just test-doc` | Use `-- --show-output` or `--nocapture` only when the test's diagnostic output is needed. Quick tests are scratch space for inspecting CST, formatter IR, or one analyzer query. Persistent behavior belongs in the subsystem's normal fixture directory before finishing. ## Snapshot Workflow Run the focused test to produce snapshots, then review every changed section: ```shell cargo insta review ``` Use `cargo insta accept` or `cargo insta reject` only after inspecting the pending changes. A passing snapshot test proves output matches the checked-in snapshot, not that the snapshot describes correct behavior. ### Orphaned Snapshots …
Read the whole file at its exact version.
How to install
mdr add modem-dev/ossrules/testing-codegen@git:20260917.a2709ecmdr add modem-dev/ossrules/testing-codegen@sha256:f15a331e9c73223bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3iz5q74edolou73p)
1 badge views in 30 days
Versions
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 (5160 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
modem-dev/ossrules · 52 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3iz5q74edolou73p GET https://markdownregistry.com/api/v1/resolve?ref=modem-dev/ossrules/testing-codegen GET https://markdownregistry.com/api/v1/blob/f15a331e9c73223b4e2e3f3f7d5fce47daedd58e7fd75b37317d5722c747685b
Your agent 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.