code-review

Reviews pull requests and diffs using Google eng-practices dimensions and an OWASP security lens.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tarabakz25/my-skills --skill code-review-tarabakz25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/tarabakz25/my-skills/tree/main/code-review
Command: npx skills add https://github.com/tarabakz25/my-skills --skill code-review-tarabakz25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often suffer from inconsistent severity labeling, missed security issues, and reviewers blocking merges over personal preference. This Skill turns code review into a repeatable workflow with a severity taxonomy, a 12-dimension checklist, and a structured verdict format. ## Core Features & Use Cases - Severity-tagged findings: Every comment is labeled Blocking, Should-fix, Nit, or Praise so authors instantly know what gates the merge. - Multi-dimension checklist: Walks the 12 Google eng-practices review dimensions plus concurrency and performance deep-dives via reference files. - OWASP security lens: Applies a security audit pass with concrete grep targets for injection, secrets, SSRF, deserialization, and auth issues. - Use Case: When asked to review a GitHub PR, the agent clones the change, reads every file in context, runs the checklist and security lens, then outputs a Summary, tagged Findings, and a verdict such as LGTM or Needs changes. ## Quick Start Ask the agent to review this pull request and produce a severity-tagged findings list with a merge verdict.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a GitHub pull request with an AI agent?▼

Ask the agent to review the PR and it clones the change, reads the PR description first, opens every changed file in full context, walks the review checklist, and applies the security lens. It outputs a summary, severity-tagged findings, and a merge verdict.

What should a code review checklist cover?▼

A thorough checklist covers design, functionality, complexity, tests, naming, comments, style, consistency, documentation, every-line reading, context, and praise. This Skill extends those 12 dimensions with concurrency deep-dives on races and deadlocks plus performance checks like N+1 queries.

How do I check a diff for security vulnerabilities?▼

Run the OWASP-flavored security lens, which greps for hardcoded secrets, string-concatenated SQL, shell injection, unsafe deserialization, SSRF, and missing authorization checks. Each hit is treated as a lead and confirmed by tracing the data flow before flagging.

Does this code review workflow work on Windows and macOS?▼

Yes, the Skill declares support for Linux, macOS, and Windows in its frontmatter. It relies on the GitHub CLI for PR access and standard shell grep patterns, which work across all three platforms.

When should I not use a full code review workflow?▼

Skip the full workflow for pure metadata questions like PR author or count, generated or vendored files which only need scanning, and quick gut-check requests where only a verdict and top three risks are wanted.