code-review-judge SKILL.md skillA
code-review-judge from heapy/kortex is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add heapy/kortex/code-review-judge@git:20260925.f46a0d7Pins git:20260925.f46a0d7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- heapy/kortex
- Path
plugins/heapy/skills/code-review-judge/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260925.f46a0d7, committed Sep 25, 2026
- First version recorded
- Sep 25, 2026
- Size
- 3,716 bytes
- Repository stars
- 7
- License
- Apache-2.0
Decide with the user which review findings to fix.
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 Review Judge Discuss each code-review finding with the user in this session. The general framework: 1. Identify the review scope: working tree, commit, branch, pull request, or path. 2. If scope is unknown or missing, ask the user. 3. Log the scope and current HEAD SHA at the top of the decision log. **Start a decision log** in a scratch file outside the repository. It should contain the full original context of every finding, including its source — the finder, agent, or reviewer that reported it — when the review names one. A long walk can outlive the context window; the log is what survives. Write each decision as soon as it is made. **Use plain words.** Write for an average developer who has not seen this codebase. Do not use jargon that only a narrow field or one language community knows. If the findings need a few key terms, define them in a short glossary before the first finding, copy it into the decision log, and use only those terms. For each finding: - Describe the conditions under which it happens, and rate their **likelihood**. - Describe its impact, and rate the **impact**. …
Read the whole file at its exact version.
How to install
mdr add heapy/kortex/code-review-judge@sha256:df5cd2e56b52942dThe line at the top of this page pins the label git:20260925.f46a0d7, 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.
[](https://markdownregistry.com/a/art_rathy37v3uvpfi52)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Sep 25, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260925.f46a0d7 latest | 2026-09-25 | f46a0d7 | 3,716 B | A | view · diff |
| git:20260925.6f9390f | 2026-09-25 | 6f9390f | 3,162 B | A | view · diff |
| git:20260925.09696c0 | 2026-09-25 | 09696c0 | 3,131 B | A | view |
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 (3716 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
heapy/kortex · 7 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rathy37v3uvpfi52 GET https://markdownregistry.com/api/v1/resolve?ref=heapy/kortex/code-review-judge GET https://markdownregistry.com/api/v1/blob/df5cd2e56b52942d744fdd78bb5875186e823bd690b24ac8f25275d95ea7a662
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.