Skills code-review-playbook
๐Ÿ“ฆ

code-review-playbook

v1.0.0 Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access

Review Code with Consistent, Actionable Feedback

Inconsistent reviews miss defects and create unclear feedback. This playbook provides structured checklists, conventional comments, templates, and review workflows for reliable decisions.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "code-review-playbook" from https://skillstore.io/skills/ariegoldkin-code-review-playbook.md and its manifest at https://skillstore.io/api/skills/ariegoldkin-code-review-playbook/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.

Test it

Using "code-review-playbook". A payment pull request confirms an order before checking whether the payment provider succeeded.

Expected outcome:

  • bug [blocking]: Verify payment success before confirming the order.
  • Impact: A failed payment can produce a completed order and incorrect fulfillment.
  • Suggestion: Handle unsuccessful responses first, then persist confirmation only after success.

Using "code-review-playbook". A self-review request includes a new endpoint, happy-path tests, and no authorization tests.

Expected outcome:

  • security [blocking]: Add authorization coverage for the new endpoint.
  • Tests should cover unauthenticated access, insufficient permissions, valid ownership, and cross-user access.
  • Readiness decision: Request review after authorization behavior and failure paths are verified.

Using "code-review-playbook". A large refactor changes a shared interface across several modules without migration notes.

Expected outcome:

  • breaking [blocking]: Document and test every consumer affected by the interface change.
  • The review should map direct consumers, indirect dependents, rollout order, and compatibility expectations.
  • Consider splitting the interface migration from unrelated cleanup to reduce review and rollback risk.

Security Audit

Safe
v9 โ€ข 7/23/2026 Open versioned report

All 64 static findings are false positives caused by prose, Markdown formatting, TypeScript examples, or a documentation link. No prompt injection, command execution, reconnaissance, data exfiltration, or unsafe network behavior was found.

4
Files scanned
1,983
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/ariegoldkin-code-review-playbook/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/ariegoldkin-code-review-playbook/security.svg)](https://skillstore.io/skills/ariegoldkin-code-review-playbook?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/ariegoldkin-code-review-playbook?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ariegoldkin-code-review-playbook/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/ariegoldkin-code-review-playbook.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

AI Agent Hub. (2026). code-review-playbook security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/ariegoldkin-code-review-playbook/audits/9

BibTeX citation

@techreport{ai-agent-hub-ariegoldkin-code-review-playbook-2026, author = {AI Agent Hub}, title = {code-review-playbook security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/ariegoldkin-code-review-playbook/audits/9}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "code-review-playbook security audit report (audit version 9)" version: "1.0.0" type: report authors: - name: "AI Agent Hub" date-released: "2026-07-23" url: "https://skillstore.io/skills/ariegoldkin-code-review-playbook/audits/9" identifiers: - type: other value: "skillstore:ariegoldkin-code-review-playbook:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
87
Content
72
Community
74
Spec Compliance

What You Can Build

Review a Pull Request

Review a change systematically, prioritize defects, and provide labeled comments that separate blocking issues from optional improvements.

Prepare Changes for Review

Run a structured self-review before requesting feedback, covering scope, tests, documentation, security, and reviewer context.

Standardize Team Reviews

Create shared review expectations, comment conventions, templates, and measurable goals for a development team.

Try These Prompts

Quick Pull Request Review
Review the following pull request using the playbook. Check correctness, readability, tests, security, and scope. Label every finding and separate blocking issues from optional suggestions.

Pull request context and diff:
[insert content]
Author Self-Review
Perform a self-review of this change. Identify missing context, risky assumptions, weak tests, documentation gaps, and unnecessary scope. Finish with a readiness checklist and required actions.

Change details:
[insert content]
Security-Focused Review
Review this change with the security checklist. Examine authorization, input validation, secrets, sensitive data, dependencies, logging, and abuse controls. Provide evidence, impact, and specific remediation for each finding.

Security context and diff:
[insert content]
Cross-File Architecture Review
Analyze this multi-file change for architectural consistency and indirect impact. Trace dependencies, contracts, breaking changes, duplicated patterns, complexity, and test coverage gaps. Rank findings by merge risk and explain tradeoffs.

Architecture context and changed files:
[insert content]

Best Practices

  • Provide the pull request purpose, requirements, diff, test results, and relevant architectural context.
  • Ask for evidence-based findings with clear impact, priority, and concrete next steps.
  • Separate merge blockers from optional improvements and re-review only the affected areas after changes.

Avoid

  • Do not request approval from a summary alone when the code and test evidence are unavailable.
  • Do not treat style preferences as blockers unless they violate an established project rule.
  • Do not combine large refactors, behavior changes, and unrelated cleanup into one review without clear boundaries.

Frequently Asked Questions

What should I provide for a useful review?
Provide the change purpose, requirements, diff, affected files, test results, and any relevant architecture or security constraints.
Does this skill execute repository tools?
No. It supplies review guidance and examples. Tests, linters, scanners, and repository commands require separate tools and explicit execution.
Which programming languages are supported?
The general process applies broadly. Detailed language checks focus on JavaScript, TypeScript, and Python.
Can the skill decide whether a pull request should merge?
It can recommend approval, comments, or requested changes. Repository owners remain responsible for merge authority and risk acceptance.
Does it replace a dedicated security review?
No. It provides a baseline security checklist. High-risk systems still need threat modeling, specialized testing, and qualified security review.
How should I review a very large change?
Review architecture and impact first, then inspect smaller logical sections. Ask the author to split unrelated work when practical.

Developer Details

License

MIT

Author version

v1.0.0

Skillstore revision

r2

Ref

89edfdc710d0846129dcee6a929477b04f08052c

Maintenance freshness

7/24/2026

Usage

8 downloads ยท 326 views

File structure

๐Ÿ“ checklists/

๐Ÿ“„ code-review-checklist.md

๐Ÿ“„ SKILL.md

๐Ÿ“ templates/

๐Ÿ“„ pr-template.md

๐Ÿ“„ review-feedback-template.md

More from AI Agent Hub

View all