Skip to content
Contact
Engineering

Requesting Code Review

obra/superpowers

Review a change in its surrounding flow, prioritize concrete defects, and explain user impact.

SKILL.md

---
name: knoveya-requesting-code-review
description: "Review a change in its surrounding flow, prioritize concrete defects, and explain user impact. Use for matching engineering work."
---

# Requesting Code Review

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Review a change in its surrounding flow, prioritize concrete defects, and explain user impact.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

Findings include evidence and do not invent failures from style preference.

## Example task

Trace a changed authorization call through every caller.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.
View all

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-requesting-code-review as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-requesting-code-review/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Trace a changed authorization call through every caller.

Verify

Findings include evidence and do not invent failures from style preference.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.