biome-code-review skillA
biome-code-review is agent-read markdown (skill) from modem-dev/ossrules: Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation..
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
# Biome Code Review Review changes read-only against business requirements and applicable behavioral, architectural, and subsystem constraints. ## Invocation Delegate completed reviews to a fresh subagent when available. Supply only: - the review scope; - the intended business requirements, including constraints the repository cannot establish. To avoid bias, omit implementation details, suspected defects, priority files, prior findings, and expected review outcomes. Review subagents must not delegate again. Without subagents, review the complete scope directly. Treat delegated findings as candidates; the parent must [validate them](#parent-validation) before confirming or acting. ## Safety Boundary Reviewers and validating parents must preserve the worktree. Authorized implementation follows validation, outside this skill. - Do not create, edit, move, or delete files. - Do not run project code, builds, tests, formatters, linters, codegen, benchmarks, package managers, LSPs, or daemons. - Do not run mutating Git or GitHub commands except the single base-branch fetch allowed below. …
Read the whole file at its exact version.
How to install
mdr add modem-dev/ossrules/biome-code-review@git:20260917.a2709ecmdr add modem-dev/ossrules/biome-code-review@sha256:b1c04d6c091428bdPin 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_hoilgltx4fckcu2l)
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 (11327 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_hoilgltx4fckcu2l GET https://markdownregistry.com/api/v1/resolve?ref=modem-dev/ossrules/biome-code-review GET https://markdownregistry.com/api/v1/blob/b1c04d6c091428bd797d97fdb0ed0613ee44ee2b6ca0559375c28bf5660f4224
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.