code-review

Review GitHub PRs across five quality axes and post annotated comments.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rodacato/kwik-e-dev --skill code-review-rodacato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/lifecycle/skills/code-review
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill code-review-rodacato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing pull requests can be time-consuming and error-prone; this skill automates and structures the multi-axis PR review using the gh CLI, helping ensure consistent quality and thorough feedback before merge.

Core Features & Use Cases

  • Fetches PR metadata and diffs via gh to evaluate changes across correctness, readability, architecture, security, and performance.
  • Generates structured review comments with file, line, severity, and rationale, and posts them back to GitHub.
  • Supports review of human- or agent-authored changes and enforces project conventions and best practices.

Quick Start

Run the code-review skill on a pull request to generate and post a multi-axis review using gh

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate pull request reviews for correctness and security?

Automated pull request reviews evaluate code changes across correctness, readability, architecture, security, and performance. The skill fetches diffs via the gh CLI and generates structured, annotated comments with file, line, severity, and rationale directly on GitHub.

Can I review agent-authored code changes on GitHub?

Yes, agent-authored code changes can be reviewed using this skill. It applies a structured five-axis evaluation to any GitHub pull request, regardless of whether the modifications were written by a human or an AI agent.

Do I need the gh CLI to run automated code reviews?

Yes, the gh CLI is required to run these automated code reviews. The skill depends on the GitHub command line interface to fetch pull request metadata and post structured review comments back to the repository.

What is the best way to structure PR feedback for merge decisions?

The best way to structure PR feedback is to evaluate changes across five axes: correctness, readability, architecture, security, and performance. This skill enforces this structured evaluation and ties findings to specific files, lines, and rationale to guide merge decisions.

How does multi-axis code review handle performance and architecture checks?

Multi-axis code review handles performance and architecture checks by fetching PR diffs and evaluating them against project conventions. It identifies specific quality issues across these domains and generates structured comments with severity and rationale.

When should I use automated review automation for pull requests?

Automated review automation should be used when you need consistent, structured quality feedback before merging. It enforces best practices and project conventions across five evaluation axes, ensuring thorough feedback for both human and agent-authored changes.