setup

Auto-detect project stacks and generate compound-engineering.local.md via interactive prompts.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/datorresb/discovery-event-platform --skill setup-datorresb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/datorresb/discovery-event-platform/tree/main/.github/skills/setup
Command: npx skills add https://github.com/datorresb/discovery-event-platform --skill setup-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to align review agents with their project's stack and desired review depth. This skill provides an interactive setup that auto-detects the stack and writes a ready-to-use compound-engineering.local.md, enabling consistent, governed code-review workflows.

Core Features & Use Cases

  • Auto-detects the project stack (Rails, Python, TypeScript, or general) and suggests appropriate reviewers.
  • Step-by-step interactive prompts to choose stack focus, review depth, and target agents for /ce:review and /ce:work.
  • Generates compound-engineering.local.md with configured review_agents and plan_review_agents to enforce standardized reviews across the team.

Quick Start

Run the interactive setup to generate compound-engineering.local.md at the project root.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I configure project review agents for a specific tech stack?

Configuring project review agents involves running an interactive setup that auto-detects your stack and generates a compound-engineering.local.md file. This file defines your selected agents for consistent code reviews.

What is the best way to auto-detect my project stack for code review configuration?

Auto-detecting your project stack is handled by an interactive setup process that scans for Rails, Python, TypeScript, or general frameworks. It then suggests appropriate reviewers based on the detected technologies.

Does the interactive setup support Python and TypeScript repositories?

Yes, the interactive setup supports Python and TypeScript repositories, along with Rails and general stacks. It automatically identifies these frameworks to suggest appropriate review agents for your project.

How do I generate a compound-engineering.local.md file for my repository?

You generate a compound-engineering.local.md file by running the interactive setup at your project root. The process uses step-by-step prompts to select review depth and focus areas, then writes the frontmatter-enabled configuration.

Can I choose the review depth and focus areas during the project configuration setup?

Yes, you can choose the review depth and focus areas during the project configuration setup. The interactive process uses step-by-step prompts to validate your inputs and customize the generated review agent settings.

Why do I need a compound-engineering.local.md file in my project root?

You need a compound-engineering.local.md file in your project root to enable standardized, governed code-review workflows for /ce:review and /ce:work. It ensures team alignment by defining configured review_agents and plan_review_agents.