ce-code-review

Orchestrate multiple reviewer personas to surface structured findings from a diff.

10|Updated Dec 13, 2016
One-click install
npx skills add https://github.com/vitallium/dotfiles --skill ce-code-review-vitallium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-code-review
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-code-review
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-code-review-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multiple reviewer personas to produce a structured, actionable code review from diffs and PRs.

Core Features & Use Cases

  • Spawns stability-tested reviewer personas to analyze code changes, surface findings, and synthesize a unified report.
  • Supports agent-mode JSON output for automation and default interactive Markdown reports for human review.

Quick Start

Activate the code-review workflow on a PR or branch to emit a structured findings report.

Frequently Asked Questions about ce-code-review

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

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

Automating code review for pull requests involves orchestrating multiple reviewer personas to analyze a diff and synthesize a unified report. This process surfaces structured findings directly from your PR changes.

What is diff analysis in a code review pipeline?

Diff analysis in a code review pipeline is the process of evaluating code changes to surface structured findings. It works by spawning reviewer personas to analyze diffs and synthesize actionable reports.

Can I get JSON output from a code review for my CI/CD pipeline?

You can get JSON output from a code review for your CI/CD pipeline by running the process in agent mode. This mode returns structured JSON artifacts, whereas the default mode outputs interactive Markdown for human review.

How do I run a code review on a standalone branch checkout?

Running a code review on a standalone branch checkout works by applying the orchestration pipeline directly to the branch diff. It analyzes the changes and produces deterministic run artifacts without needing a full pull request.

Does the code review orchestration pipeline support plan discovery?

The code review orchestration pipeline supports optional plan discovery before spawning reviewer personas. This allows the pipeline to map out the validation steps before analyzing the diff and generating artifacts.