review

Evaluate pull requests and post Approve or Changes Requested verdicts.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill review-apokamo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/review
Command: npx skills add https://github.com/apokamo/kaji --skill review-apokamo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs the initial code review for PRs and posts an Approve / Changes Requested verdict. This skill is intended for new reviews only; fixes after /pr-fix are handled by /pr-verify. The workflow context integrates with review-close and review-cycle, and can be invoked as a fallback through review-poll.

Core Features & Use Cases

  • Evaluates PR scope, design conformance, and code quality against project standards.
  • Posts formal verdicts (Approve or Changes Requested) via kaji pr review to drive automation.
  • Works within review workflows (review-close / review-cycle), using BACK_FALLBACK via review-poll as needed.

Quick Start

Run the review skill on a target PR to perform the initial assessment and post the verdict.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate initial code review for pull requests?

Automating initial code review for pull requests involves evaluating PR scope, design conformance, and code quality against project standards. This skill automates that initial PR assessment by inspecting the diff and posting a formal Approve or Changes Requested verdict to drive workflow automation.

How does automated PR review handle code quality and design conformance?

Automated PR review handles code quality by inspecting the worktree diff and evaluating it against project standards. It checks the PR scope and design conformance, then submits a final verdict of Approve or Changes Requested based on the evaluation criteria.

What is the best way to post an Approve or Changes Requested verdict on a new PR?

The best way to post an Approve or Changes Requested verdict is through an automated review workflow that evaluates the pull request. This skill performs the initial assessment and posts the formal verdict using the kaji pr review command to drive subsequent automation.

Can I use automated code review for fixing pull requests after changes are requested?

Automated code review for fixing pull requests after changes are requested is not handled by this initial review skill. Fixes applied after a review action are handled by a separate verification step, while this skill focuses solely on new PR assessments and posting initial verdicts.

Does automated PR review work within continuous review workflows and fallback polling?

Automated PR review works within continuous review workflows like review-close and review-cycle. It can also be invoked as a fallback path through review-poll, integrating into broader automation by enforcing a defined input flow from PR resolution to final verdict submission.

What are the limitations of using automated initial PR review for ongoing code changes?

Limitations of automated initial PR review include its restriction to new reviews only. It does not handle subsequent fixes or verification cycles after changes are requested, serving strictly as the initial assessment and verdict posting mechanism within a larger review workflow.