review-cycle

Launch the review-cycle workflow via kaji run and output a PASS or ABORT verdict.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slash command wrapper that launches the review-cycle workflow via kaji run and outputs a verdict that includes guidance to run /issue-close after completion.

Core Features & Use Cases

  • Launches the review-cycle workflow: kaji run .kaji/wf/review-cycle.yaml <issue_id>.
  • Outputs a verdict block with PASS/ABORT and actionable guidance to close the issue.
  • Handles missing arguments and configuration issues with diagnostic messages to aid debugging.

Quick Start

Invoke /review-cycle <issue_id> to start the workflow and receive guidance to close the issue after completion.

Frequently Asked Questions about review-cycle

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

FAQPage Schema
How do I automate a PR review workflow with a single slash command?

You can automate a PR review workflow by invoking a slash command that triggers the review-cycle. It launches the kaji run workflow, evaluates the pull request, and outputs a PASS or ABORT verdict with diagnostic details.

How do I close an issue automatically after a code review passes?

To close an issue after a code review, the review-cycle outputs a verdict block containing actionable /issue-close guidance. This directs you to execute the issue-close command once the workflow reports a successful PASS outcome.

What do I need to configure before running a kaji review-cycle workflow?

Before running a kaji review-cycle workflow, you need a valid issue_id, a proper .kaji/wf/review-cycle.yaml workflow configuration file, and a functioning kaji CLI installed in your environment as described by the repository docs.

Why does my slash command workflow fail to launch the code review?

Your slash command workflow may fail due to missing arguments or configuration issues. The command handles these by outputting diagnostic messages to aid debugging, helping you identify missing issue IDs or invalid workflow files.

What does the verdict output look like when an automated code review aborts?

When an automated code review aborts, the verdict output reports ABORT and includes diagnostic details explaining the failure. It provides actionable guidance to help you resolve the identified issues before attempting another review cycle.