setup

Configure project-level settings for compound-engineering workflows.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill setup-jaydubya818
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/compound-engineering/plugins/compound-engineering/skills/setup
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill setup-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure project-level settings for compound-engineering workflows. Currently a placeholder — review agent selection is handled automatically by ce:review.

Core Features & Use Cases

  • Automatic review agent selection for project-level code reviews using ce:review.
  • Placeholder for future per-project configuration needs beyond review agent selection.
  • Guidance for when to modify CLAUDE.md or AGENTS.md to reflect project-specific contexts.

Quick Start

Invoke the setup skill to apply project-level configuration for compound-engineering workflows.

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 settings for compound-engineering workflows?

Project-level setup for compound-engineering workflows centralizes review-agent selection and minimizes per-project configuration during initialization. It aligns code-review agent behavior with diff contexts automatically.

When do I need to modify CLAUDE.md or AGENTS.md for project-specific contexts?

You modify CLAUDE.md or AGENTS.md when you need to reflect project-specific contexts beyond the default automated review-agent selection. The setup skill provides guidance for these customizations.

Does review agent selection require manual configuration for each project?

No, review agent selection is handled automatically by ce:review. The setup skill currently acts as a placeholder, centralizing selection so you defer per-project customization until future needs arise.

What is the best way to minimize per-project configuration for code reviews?

The best way to minimize per-project configuration is invoking the setup skill during project initialization. It centralizes review-agent selection and aligns code-review agent behavior with diff contexts automatically.

What are the limitations of automating project setup for code reviews?

The setup skill is currently a placeholder for future per-project configuration needs. It centralizes review-agent selection but defers all other customization until specific project requirements emerge.