Agent skill · writing content · yonatangross
code-review-playbook
Review process, conventional comments, language checklists and feedback templates. Use when reviewing code or standardizing review practice. To review a PR end to end, use review-pr.
Why this skill is useful
Provides structured review processes and language-specific checklists that improve code quality and consistency in reviews.
What it needs
About 5k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
Code Review Playbook This skill provides a comprehensive framework for effective code reviews that improve code quality, share knowledge, and foster collaboration. Whether you're a reviewer giving feedback or an author preparing code for review, this playbook ensures reviews are thorough, consistent, and constructive. Overview Reviewing pull requests or merge requests Preparing code for review (self-review) Establishing code review standards for teams Training new developers on review best practices Resolving disagreements about code quality Improving review processes and efficiency Upstream coverage (do not restate) This skill is a thin wrapper. General review craft is documented first-party elsewhere; only OrchestKit's own decisions live here. Load Read("references/ork-delta.md") for the house rules that survived the retired files. Topic Go here instead ------- ----------------- Review philosophy, speed, tone, PR sizing https://google.github.io/eng-practices/review/ Conventional comment labels and decorations references/conventional-comments.md, https://conventionalcomments.org/ OWASP Top 10 review checks rules/security-baseline.md, https://owasp.org/Top10/ Generic language and framework review checklists rules/typescript-quality.md, rules/python-quality.md, rules/linting-biome-rules.md Review report shape and multi-agent full-PR review ork:review-pr Applying findings to the working tree /code-review --fix, /simplify (see below) Security-only pass over the current branch /security-review GitHub review mechanics (approve, request changes, inline comments) https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests --- Conventional Comments Load Read("references/conventional-comments.md") for the full format, labels (praise, nitpick, suggestion, issue, question, security, bug, breaking), decorations ([blocking], [non-blocking], [if-minor]), and examples. --- Review Process 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/code-review-playbook