setup

Configure project-wide settings for ce-review agent selection workflows.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/vib795/copilot-anatomy --skill setup-vib795
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/setup
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill setup-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure project-wide settings for compound-engineering review workflows to reduce per-repository configuration.

Core Features & Use Cases

This skill provides a centralized project-level configuration point to control review agent selection, with ce-review handling the automatic reviewer assignment based on diffs. It does not require per-project configuration for code reviews, and is intended as a placeholder for future, extended configuration (CLAUDE.md or AGENTS.md contexts).

Quick Start

Activate the skill to rely on ce-review for automatic reviewer selection based on diffs.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I configure project-wide settings for compound-engineering review workflows?

Project-wide configuration for compound-engineering review workflows is centralized to reduce per-repository setup, relying on ce-review to automatically handle review agent selection based on diffs. This reduces per-repository configuration.

Do I need per-project configuration for code reviews in a multi-repo environment?

Per-project configuration for code reviews is not required in a multi-repo environment when using this setup. It disables per-project model invocation, relying on ce-review for automatic reviewer assignment based on diffs.

How does automatic review agent selection work based on code diffs?

Automatic review agent selection based on code diffs is handled by ce-review. This setup acts as a centralized configuration point to apply that selection across a multi-repo environment without requiring per-repository configuration.

Can I use CLAUDE.md or AGENTS.md contexts for project-level configuration?

CLAUDE.md or AGENTS.md contexts are intended as future extensions for this project-level configuration. Currently, the setup acts as a placeholder to control review agent selection and disable per-project model invocation.

Why should I use a centralized configuration point for review workflows?

A centralized configuration point for review workflows reduces per-repository configuration overhead in multi-repo environments. It provides a future-ready setup to control ce-review agent selection and disable per-project model invocation.