agentsclimarketplace

Requesting code review

Skill charlieviettq/awesome-agent-skill/.cursor/skills/core-workflow/requesting-code-review

Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).

Install
npx -y skills add charlieviettq/awesome-agent-skill --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

  • 22 stars22 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

Request a focused code review with scope, diff context, and severity-ordered findings. Use before merge or between plan tasks when quality gate is needed. Triggers: "request review", "review my diff", "pre-merge review", "second pair of eyes".

SKILL.md

2.0 KB, as published. Nobody here has run it

Requesting code review

When to use

  • Before landing a significant PR or slice
  • After completing a plan task that touches shared contracts
  • When risk is high (auth, money, data migration, agent tools)

When not to use

  • Trivial typo-only changes with no behavior impact
  • User explicitly wants speed over review

Prepare review packet

  1. Scope — what changed and what was intentionally out of scope
  2. Base — branch name and commit range or PR link
  3. Risk areas — files or behaviors reviewers should scrutinize
  4. Verification already run — commands + outcomes (paste evidence)
  5. Questions — specific uncertainties for the reviewer

Review request template

## Review request
- **Scope:**
- **Base / range:**
- **Risk areas:**
- **Verification run:**
- **Open questions:**
- **Severity scale:** Critical / High / Medium / Low / Nit

Using a reviewer subagent (optional)

Only when user or parent agent explicitly allows subagents:

  • Pass the packet above; do not pass unrelated context
  • Ask for findings ordered by severity with file:line references
  • Parent agent integrates findings; subagent does not merge or push

For deep structural review, gstack/code-quality/review may be used as an optional supplement.

After review

  • Triage findings with receiving-code-review
  • Re-run verification before claiming addressed

Anti-patterns

  • "Please review everything" with no scope
  • Starting review before tests pass locally
  • Treating nitpicks as blockers without trade-off discussion

Related

receiving-code-review, verify-before-done, doubt-driven-review, github-comment-triage

Patterns inspired by obra/superpowers (MIT).

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.