agentsclimarketplace
Sign in

Requesting code review

Skill heymegabyte/claude-skills/20-superpowers/requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirementsFrom its SKILL.md

Install
npx -y skills add heymegabyte/claude-skills --skill requesting-code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 337 tokens by cl100k_base, as published. Nobody here has run it

Requesting Code Review

Dispatch a reviewer subagent on completed work. Feed it crafted context (description + requirements + git range) — never your session history. Keeps the reviewer on the work product and preserves your own context.

Review early, review often.

Brian's stack already ships a purpose-built code-reviewer agent + the Agent Diversity Review gate ([[agent-selection]]). Prefer the named agent over a bare general-purpose spawn; this skill is the request protocol that complements both.

When to request

Mandatory:

  1. Before merge to main
  2. After each task in subagent-driven development
  3. After completing a major feature

Optional: when stuck (fresh eyes), before a refactor (baseline), after a complex bugfix.

How to request

  1. Get SHAs — BASE_SHA=$(git rev-parse origin/main), HEAD_SHA=$(git rev-parse HEAD).
  2. Spawn the code-reviewer agent (or general-purpose filling code-reviewer.md).
  3. Fill placeholders: {DESCRIPTION} (what you built), {PLAN_OR_REQUIREMENTS} (what it should do), {BASE_SHA}, {HEAD_SHA}.

Act on feedback

  1. Fix Critical immediately; fix Important before proceeding.
  2. Note Minor for later.
  3. Push back with technical reasoning if the reviewer is wrong — see [[receiving-code-review]].

Never

  • Skip review because "it's simple".
  • Ignore Critical, or proceed with unfixed Important.
  • Argue with valid technical feedback.
<!-- budget: ~40 -->

What ships with it: 1 file

2.9 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.