# Requesting Code Review

> Use after completing meaningful implementation work in Cursor and before merging or declaring the change ready, so the result gets a focused review for bugs, regressions, and maintainability risks.

- Skill: `6bnbn/requesting-code-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 6bnbn/requesting-code-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/6bnbn/requesting-code-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 6bnbn (https://skillmd.com/u/6bnbn)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/6bnbn/requesting-code-review

---

# Requesting Code Review

## Goal
Ask for a focused review at the right time, with the right scope.

## When To Use
- After finishing a substantial feature or bug fix
- Before merging or creating a pull request
- After a risky refactor
- When local changes affect behavior, API contracts, or UI flows

## How To Ask
Provide:
- what changed
- which files or diff should be reviewed
- what behavior matters most
- any specific concerns such as accessibility, regressions, or edge cases

## Good Prompt Shape
- "Review the changed files for real bugs and regressions."
- "Review this branch diff and focus on API behavior and edge cases."
- "Review this UI change for accessibility and misleading interaction states."

## After Review
- Fix high-severity issues first.
- Clarify or push back when a suggestion does not fit the codebase.
- Re-run relevant verification before declaring the work ready.