requesting-code-review
Request Code Reviews Before Merge
Unreviewed changes can ship bugs, regressions, or incomplete requirements. This skill guides Claude, Codex, and Claude Code to request structured review before merge.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "requesting-code-review" from https://skillstore.io/skills/obra-requesting-code-review.md and its manifest at https://skillstore.io/api/skills/obra-requesting-code-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "requesting-code-review". Review a completed verification feature before continuing to the next task.
Expected outcome:
The review lists specific strengths, identifies an important user feedback gap, notes a minor maintainability issue, and recommends fixes before proceeding.
Using "requesting-code-review". Check whether a change is ready to merge after a bug fix.
Expected outcome:
The response compares the change to the stated requirement, separates critical and minor findings, and gives a clear merge verdict.
Using "requesting-code-review". Ask a subagent to inspect a diff range for test and architecture risks.
Expected outcome:
The review summarizes architecture quality, flags missing tests where relevant, and explains why each issue affects production readiness.
Security Audit
SafeAll static findings were adjudicated as false positives. The command-like examples are read-only git workflow instructions, and the other hits are ordinary review-template text. No prompt injection, exfiltration intent, or unsafe automation was found in the reviewed files.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/obra-requesting-code-review/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/obra-requesting-code-review?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/obra-requesting-code-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/obra-requesting-code-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/obra-requesting-code-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
obra. (2026). requesting-code-review security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/obra-requesting-code-review/audits/8BibTeX citation
@techreport{obra-obra-requesting-code-review-2026,
author = {obra},
title = {requesting-code-review security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/obra-requesting-code-review/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "requesting-code-review security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "obra"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/obra-requesting-code-review/audits/8"
identifiers:
- type: other
value: "skillstore:obra-requesting-code-review:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
9 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
dmjgilbert-requesting-code-review
2026-09-09
obra-requesting-code-review
2026-09-09
cycleaddict-requesting-code-review
2026-09-09
sickn33-requesting-code-review
2026-09-09
codingcossack-requesting-code-review
2026-09-09
cygnusfear-requesting-code-review
2026-09-09
davila7-requesting-code-review
2026-09-09
dyai2025-requesting-code-review
2026-09-09
zhanlincui-requesting-code-review
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review Feature Work
Request a structured review after completing a feature, before the next task starts.
Check Merge Readiness
Use the checklist to confirm requirements, tests, and production concerns before merging.
Coordinate Subagent Reviews
Send a clear diff range and plan reference to a dedicated code-reviewer subagent.
Try These Prompts
Request a code review for my latest completed task. Use the requesting-code-review workflow and ask me for any missing SHAs or requirements.
Review the completed change against this plan: [requirements]. Check correctness, test coverage, and any missing requirement.
Before merge, review the implementation for production readiness. Categorize findings as critical, important, or minor, then give a clear merge assessment.
Use the code-reviewer template to review the git range from [base SHA] to [head SHA] against [plan]. Report strengths, issues by severity, recommendations, and readiness.
Best Practices
- Provide the base SHA, head SHA, and requirement source before requesting review.
- Ask for file and line references so every issue can be verified.
- Fix critical and important findings before starting the next task.
Avoid
- Requesting a vague approval without a diff range or requirements.
- Treating minor style comments as blockers while ignoring real defects.
- Continuing development after valid important findings remain unresolved.
Frequently Asked Questions
When should I use this skill?
Does it run the review automatically?
What information should I provide?
Can it work with Claude, Codex, and Claude Code?
How should I handle critical findings?
What if the reviewer is wrong?
Developer Details
Author
obraLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
62e2a730c5cd74eab4c7164309d810de660fcea3
Maintenance freshness
7/18/2026
Usage
10 downloads · 234 views
File structure