requesting-code-review skillA
requesting-code-review is agent-read markdown (skill) from yeaight7/agent-powerups: Use when completing tasks, implementing major features, or before merging to verify work meets requirements..
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
# Requesting Code Review ## Purpose Dispatch a focused reviewer with enough context to catch bugs, requirement gaps, and risky assumptions before merge. ## When to Use - After a major feature - Before merge - After a complex bug fix - During multi-task execution when review checkpoints matter ## Requirements Preferred inputs: - local git range - written requirements or plan Helpful check: ```bash git rev-parse --is-inside-work-tree ``` ## Inputs - What was implemented - Requirements or plan - Base and head revisions, if available ## Workflow 1. Get the git range when local git is available. ```bash git rev-parse origin/main git rev-parse HEAD ``` 2. Dispatch a reviewer using `references/code-reviewer.md`. 3. Include summary, requirements, and diff range. 4. Fix critical issues first, then important ones. ## Output - strengths - critical, important, and minor issues - recommendations - merge readiness assessment ## Verification - [ ] Reviewer received requirements or plan - [ ] Reviewer received a diff range or equivalent context - [ ] Critical issues were not ignored - [ ] Important issues were resolved or explicitly deferred ## Failure Modes - skipping review …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/requesting-code-review@git:20260606.3a4ceffmdr add yeaight7/agent-powerups/requesting-code-review@sha256:8579571a7277e9bcPin 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_ooxvtmzehutm56fh)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.3a4ceff latest | 2026-06-06 | 3a4ceff | 1,655 B | A | view · diff |
| git:20260502.d03eb5d | 2026-05-02 | d03eb5d | 1,667 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 (1655 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ooxvtmzehutm56fh GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/requesting-code-review GET https://markdownregistry.com/api/v1/blob/8579571a7277e9bc0e937361207e26d39370457bbec8c72a59db50ca16c34986
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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups