Implement, fix, simplify, refactor, or review code with evidence-based reuse, clear ownership, precise types, focused tests, and removal of accidental complexity. Use for substantive code changes and code-quality reviews. Skip prose-only, generated-only, dependency-only, or purely mechanical edits.
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
# Code quality
Build the smallest clear solution that fully satisfies the approved behavior.
Understand the system before shortening it. Repository contracts and explicit
user decisions take precedence over generic style preferences.
## Establish the scope
- Use the user-named scope. Otherwise use the current task's changed files or
branch diff. If neither exists, ask for scope rather than auditing the repo.
- Infer the mode: implementation, bug fix, simplification, or review. A review
request authorizes findings, not edits. Simplification preserves required
behavior; an approved behavior change implements the intended end state.
- Preserve unrelated work. Read applicable guidance, relevant call paths, tests,
and history only where they resolve a concrete uncertainty.
- Establish required behavior, failure handling, domain rules, and verification
before editing. Do not turn a clear task into a planning ceremony.
## Find the owner before adding code
Search in this order: existing project behavior and patterns, platform or
standard library, installed dependencies, then new code or a dependency.
…
The line at the top of this page pins the label git:20261015.a434746, 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_y6shzj7xkfhibtju
GET https://markdownregistry.com/api/v1/resolve?ref=bjornmelin/dev-skills/code-quality
GET https://markdownregistry.com/api/v1/blob/49787b8d70051f8c8fb2319f4c36c9429c527f38084773e9971282248a63d492
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.
bjornmelin/dev-skills · archive/skills/browser-workbench-setup/SKILL.md · Set up browser automation and UI QA for a new repository using playwright-interactive as the primary interactive tool…
bjornmelin/dev-skills · archive/skills/bun-audit/SKILL.md · Shared Bun audit/remediation router. Use when auditing a repo for Bun-first correctness, explaining findings, listing…
bjornmelin/dev-skills · archive/skills/managing-tech-debt/SKILL.md · Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring…
seedcord/seedcord · .agents/skills/code-quality/SKILL.md · Use this when asked to write code, or audit, sweep, or fix code quality across the seedcord monorepo. Covers the…
smixs/code-quality-skill · skills/code-quality/SKILL.md · Code quality advisor for a repo: one bun script behind git hooks and Claude Code, Codex, Grok, pi, omp, and OpenCode…
cooneycw/claude-power-pack · .claude/skills/code-quality/SKILL.md · Code review, testing and quality patterns. Use when reviewing code, deciding what testing a change needs, or judging…
