Skill Pantry · Gaiya365

Development

Requesting Code Review

Ask for a focused second look at a concrete code change.

DevelopmentMITChecked Oct 18, 2026

Our review

This skill defines when to request an independent review and how to give a reviewer enough context: the task, the base and head revisions, changed files, and the standards that matter. A companion reviewer prompt provides an explicit structure for reporting problems. It is designed for agent workflows where review can happen before defects spread to later tasks.

Use it after a substantial implementation or before merging a branch. Skip a separate review pass for a trivial edit when the project does not require one. The process assumes a subagent or reviewer is available; if one is not, a human review or targeted self-check may be more appropriate. A review comment is still a hypothesis to verify against code and requirements.

The folder contains text files only. The SKILL.md shows local Git commands to identify revisions and asks an agent to dispatch another agent; that may consume model resources but is not a bundled script. It does not require a network call unless the chosen review workflow posts or fetches from a remote service.

For installation, open the linked maintainer folder and read its current SKILL.md, license, and supporting files. Copy the complete folder to a skills location your agent documents, or use an installer your agent supports. Begin with a small, low-risk task and confirm that the agent loaded the intended version. Our install guide covers those checks.

Source and license

Maintainer: Jesse Vincent / obra. Checked: October 18, 2026. The maintainer controls this repository; the current files may differ from the version we reviewed.

Repository ↗ · SKILL.md ↗ · MIT license ↗

← Browse all skills