domains / families / software-engineering / requesting-code-review

requesting-code-review

combined

Use when completing tasks, implementing major features, or before merging to verify work meets requirements Prepare and request a code review after implementation or before merge by assembling scope, requirements, git range, and reviewer instructions.

When to use

• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies share the same core workflow (get SHAs, dispatch a code-reviewer subagent, act on feedback), but they disagree on the subagent type and template placeholders, and each adds material constraints the others lack. obra/superpowers is the most complete and self-contained (it names a general-purpose subagent, includes a 'Common Rationalizations' section, and uses a 4-placeholder template). foryourhealth111-pixel/Vibe-Skills adds a 'Routing Boundary' that separates this skill from code-reviewer and receiving-code-review, plus an 'Integration with Workflows' section. sickn33/agentic-awesome-skills and LeoYeAI/openclaw-master-skills are near-identical mirrors that use a 5-placeholder template and a superpowers:code-reviewer subagent type, and sickn33 adds generic 'When to Use' and 'Limitations' sections. Crowning one copy would hide the routing boundary, the workflow integration guidance, and the placeholder/subagent-type disagreement.