setup

Guide contributors to rely on ce:review's automatic reviewer selection.

Updated Nov 11, 2023

Search Tags:#automation #documentation #workflow-guidance #compound-engineering #project-configuration #review-agent

Ready to run

npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill setup-michaelvolz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/setup
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill setup-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents teams from wasting time on obsolete per-project review agent configuration when the ce:review skill already auto-selects reviewers.

Core Features & Use Cases

Automated Guidance: Informs contributors that the latest compound-engineering workflow handles reviewer selection without project-specific overrides.
Future-Proof Placeholder: Reserves a consistent entry point for any future project-level configuration needs beyond review selection.
Use Case: When developers notice a changelist, they can run this skill to confirm no further review configuration is required and be redirected to CLAUDE.md or AGENTS.md for context.

Quick Start

Ask setup to explain that review agent configuration is handled automatically by ce:review so no manual settings are needed.

Frequently Asked Questions about setup

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

FAQPage Schema

Do I need to manually configure review agents for each project?▼

Manual review agent configuration is not needed because the ce:review skill automatically selects reviewers for diffs using a tiered selection process.

How does automated reviewer selection work in compound-engineering workflows?▼

Automated reviewer selection in compound-engineering workflows operates through ce:review's tiered selection mechanism, which auto-selects reviewers for diffs without requiring project-specific overrides.

Where should I document project context instead of configuring review agents?▼

You should document project context in CLAUDE.md or AGENTS.md files, which provide the necessary environment information while ce:review handles reviewer selection automatically.

What happens when I run the setup skill on a changelist?▼

Running the setup skill on a changelist confirms that no manual review configuration is required and redirects you to CLAUDE.md or AGENTS.md for project context documentation.

Can I override the automatic reviewer selection for specific projects?▼

The setup skill eliminates redundant per-project review agent configuration, serving as a future-proof placeholder that currently redirects all reviewer selection to ce:review's automated tiered process.

Why does my project still ask for review agent configuration?▼

Project review agent configuration prompts are obsolete because ce:review already handles reviewer selection automatically; you should instead document context in CLAUDE.md or AGENTS.md.