setup

Configure project-level workflow settings for compound-engineering pipelines.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill setup-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/setup
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill setup-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure project-level configuration for compound-engineering workflows, clarifying that per-project review configuration is no longer required as ce-review handles agent selection automatically.

Core Features & Use Cases

  • Centralizes project-level configuration for compound-engineering workflows.
  • Documents how ce-review automates reviewer selection and how project-specific review context belongs in CLAUDE.md or AGENTS.md.
  • Use Case: A team wants to standardize review agent behavior across multiple repos without per-project tweaks.

Quick Start

Rely on ce-review to automatically select reviewers based on diffs; no per-project configuration is required.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I configure project-level workflow settings for compound-engineering pipelines?

Project-level workflow configuration is centralized by reserving project settings for future extensibility. Standardized configuration is applied directly to compound-engineering pipelines, ensuring consistent behavior across repositories without requiring manual per-project tweaks.

Do I need per-project configuration for review agents?

Per-project configuration for review agents is no longer required. The ce-review component automates reviewer selection based on diffs, eliminating the need for manual project-specific review configuration and simplifying setup across multiple repositories.

What is the best way to standardize review agent behavior across multiple repositories?

The best way to standardize review agent behavior is to rely on centralized project-level configuration combined with ce-review. This automates reviewer selection globally, while project-specific review context belongs in CLAUDE.md or AGENTS.md files instead of local config.

Where should project-specific review context go instead of per-project configuration?

Project-specific review context belongs in CLAUDE.md or AGENTS.md files. This approach separates contextual instructions from automated pipeline configuration, allowing ce-review to dynamically select reviewers based on diffs without manual configuration overrides.

Can I use ce-review to automate reviewer selection based on code diffs?

Yes, ce-review automatically selects reviewers based on code diffs. This automation removes the need for per-project configuration, dynamically matching review agents to changes while centralized project settings handle broader workflow standardization.

Why does my compound-engineering pipeline no longer require per-project review configuration?

Per-project review configuration is obsolete because ce-review now handles agent selection automatically. This architectural shift centralizes workflow settings, relying on diff-based analysis to route reviews, which reduces configuration overhead and future-proofs project settings.