agentsclimarketplace
Sign in

Requesting code review

Skill yeaight7/agent-powerups/skills/requesting-code-review

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

Install
npx -y skills add yeaight7/agent-powerups --skill requesting-code-review

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

One thing to look at

  • 6 stars6 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, 326 tokens by cl100k_base, as published. Nobody here has run it

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:

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.
git rev-parse origin/main
git rev-parse HEAD
  1. Dispatch a reviewer using references/code-reviewer.md.
  2. Include summary, requirements, and diff range.
  3. 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
  • incomplete diff context
  • ignoring critical issues
  • accepting feedback blindly

Missing Dependency Behavior

If local git range is unavailable:

  1. Say local git context is missing.
  2. Ask for an explicit diff, patch, or file list.
  3. Do not pretend a git-based review scope was provided.

What ships with it: 1 file

2.1 KB alongside SKILL.md

references/

Gives 2 of the 12 instructions most code review skills give in 326 tokens

Counted across 668 of the 814 authors here whose files we hold, read 2026-09-06

  • Provide technical reasoning when pushing backin 84 of 668, across 70 files
  • Fix critical issues immediatelyhere, and in 77 of 668, across 60 files
  • Dispatch a code reviewer subagenthere, and in 76 of 668, across 59 files
  • Fix important issues before proceedingin 73 of 668, across 56 files
  • Ask for clarification on unclear itemsin 68 of 668, across 56 files
  • Verify feedback against codebase before implementationin 66 of 668, across 55 files
  • Implement fixes one at a timein 64 of 668, across 53 files
  • Test each fix individuallyin 62 of 668, across 51 files
  • Restate technical requirements in own wordsin 57 of 668, across 46 files
  • Reply to inline comments in the specific threadin 51 of 668, across 40 files
  • Note minor issues for laterin 49 of 668, across 34 files
  • Group findings by severityin 48 of 668, across 47 files

Said here and by no other author read

  • Get the git range when local git is available
  • Include summary requirements and diff range
  • State if local git context is missing
  • Ask for an explicit diff patch or file list

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.