agentsclimarketplace

Requesting code review

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

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

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.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.6 KB, 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.

Keep looking

Skills are one crate of 328,083. 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.