requesting-code-review SKILL.md skillA
requesting-code-review from brunob54/superpowers-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add brunob54/superpowers-orchestrator/requesting-code-review@git:20260919.897a669Pins git:20260919.897a669 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- brunob54/superpowers-orchestrator
- Path
skills/requesting-code-review/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260919.897a669, committed Sep 19, 2026
- First version recorded
- Mar 15, 2026
- Size
- 6,117 bytes
- Repository stars
- 3
- License
- MIT
Structured code review against requirements, quality, and security standards. Invoke after meaningful code changes or before merge. Triggers on: "review my code", "code review", "check this before merge", "security review", "is this secure", "look over my changes", "second pair of eyes", "check the diff". Routed by using-superpowers or executing-plans after implementation.
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
# Requesting Code Review
Request review early to catch issues before they spread.
## When
- After completing a plan task or batch
- After major refactor/feature work
- Before merge or PR finalization
## How
1. Determine review range (`BASE_SHA` -> `HEAD_SHA`).
2. Check for `context-snapshot.json` at the project root:
- If present: run `git rev-parse HEAD` and compare to `git_hash` in the file.
- **Hashes match (fresh):** use `changed_files` and `blast_radius` as the review scope. Inject this summary into the code-reviewer prompt: *"Changed files: [list]. Also referenced by: [blast_radius callers]."*
- **Hashes differ (stale):** note the snapshot is from a previous commit; use `changed_files` as a starting point but do not rely on `blast_radius`.
- If absent: determine scope from `git diff --name-only BASE_SHA..HEAD_SHA` directly.
3. Dispatch `superpowers-orchestrator:code-reviewer` using `requesting-code-review/code-reviewer.md`.
4. Provide:
- What changed (from context snapshot or `git diff --no-ext-diff --no-textconv`)
- Scoped file list (changed files + blast radius callers if fresh snapshot available, or broad if not)
…Read the whole file at its exact version.
How to install
mdr add brunob54/superpowers-orchestrator/requesting-code-review@sha256:9080c6ba7b3f9efbThe line at the top of this page pins the label git:20260919.897a669, 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_sxqxmdljlzhya6r7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Mar 15, 2026 and Sep 19, 2026, about one every 38 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.897a669 latest | 2026-09-19 | 897a669 | 6,117 B | A | view · diff |
| git:20260815.dcd9fd0 | 2026-08-15 | dcd9fd0 | 6,087 B | A | view · diff |
| git:20260325.1b3a95f | 2026-03-25 | 1b3a95f | 6,081 B | A | view · diff |
| git:20260323.5f620fc | 2026-03-23 | 5f620fc | 6,014 B | A | view · diff |
| git:20260320.0447366 | 2026-03-20 | 0447366 | 5,263 B | A | view · diff |
| git:20260315.38413b0 | 2026-03-15 | 38413b0 | 4,676 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 (6117 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
brunob54/superpowers-orchestrator · 3 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sxqxmdljlzhya6r7 GET https://markdownregistry.com/api/v1/resolve?ref=brunob54/superpowers-orchestrator/requesting-code-review GET https://markdownregistry.com/api/v1/blob/9080c6ba7b3f9efb72adebb8ebc7850c6b9f9a5ee3030473c00327c476874b3a
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.
More from brunob54/superpowers-orchestrator
Every file in brunob54/superpowers-orchestrator