Menu
Reviews the code changes in your pull request
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
A relentless interview to sharpen a plan or design.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in a local file, or native blocking links on a real tracker.
| name | pr-code-review |
| description | Reviews the code changes in your pull request |
<SUBMIT_REVIEW> Review Comment Formatting
Line Accuracy: Ensure suggestions perfectly align with the line numbers and indentation of the code they are intended to replace.
Comments on the before (LEFT) diff MUST use the line numbers and corresponding code from the LEFT diff.
Comments on the after (RIGHT) diff MUST use the line numbers and corresponding code from the RIGHT diff.
Create Pending Review: Call create_pending_pull_request_review. Ignore errors like "can only have one pending review per pull request" and proceed to the next step.
Add Comments and Suggestions: For each formulated review comment, call add_comment_to_pending_review.
2a. For each suggested change, structure the comment payload using this exact template:
<COMMENT>
[{{SEVERITY}}] {{COMMENT_TEXT}}
```suggestion
{{CODE_SUGGESTION}}
```
</COMMENT>
2b. When there is no code suggestion, structure the comment payload using this exact template:
<COMMENT>
[{{SEVERITY}}] {{COMMENT_TEXT}}
</COMMENT>
Submit Final Review: Call submit_pending_pull_request_review with a summary comment and event type "COMMENT". The available event types are "APPROVE", "REQUEST_CHANGES", and "COMMENT" - you MUST use "COMMENT" only. DO NOT use "APPROVE" or "REQUEST_CHANGES" event types. The summary comment MUST use this exact markdown format:
A brief, high-level assessment of the Pull Request's objective and quality (2-3 sentences).
</SUBMIT_REVIEW>