setup

Configure project-level settings for compound-engineering workflows via YAML frontmatter.

6|Updated Jan 29, 2023
One-click install
npx skills add https://github.com/rethinkhealth/glion --skill setup-rethinkhealth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/setup
Command: npx skills add https://github.com/rethinkhealth/glion --skill setup-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Placeholder for project-level configuration in compound-engineering workflows; discovery and initial agent selection is automated by ce:review, so no per-project config is required.

Core Features & Use Cases

  • Provides a centralized placeholder for future project-level settings.
  • Lets ce:review automatically select reviewers based on diff content and project context.
  • Serves as a safe default for teams implementing compound-engineering workflows.

Quick Start

Use ce:review to auto-select reviewers for the current diff.

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 engineering workflows for code review?

Configure project-wide engineering workflows by applying project-level settings via YAML frontmatter. This provides a centralized placeholder for repository-wide review scenarios, guiding automatic reviewer assignment without relying on external scripts.

How does automatic reviewer assignment work for code diffs?

Automatic reviewer assignment for code diffs works by selecting reviewers based on diff content and project context. The configuration acts as a placeholder, letting the compound-engineering review process handle discovery and agent selection automatically.

Do I need per-project configuration for code-diff based agent selection?

No per-project configuration is required for code-diff based agent selection. The compound-engineering review process automates discovery and initial agent selection, making this configuration a safe default that serves as a centralized placeholder for future settings.

Can I extend project configuration with external scripts for engineering workflows?

You can extend project configuration for engineering workflows using optional scripts, references, and assets directories. The base configuration specifies a minimal, self-contained setup via YAML frontmatter and does not depend on these external scripts to function.

What is the best way to set up a safe default for compound-engineering review?

The best way to set up a safe default for compound-engineering review is applying minimal YAML frontmatter configuration. It provides a centralized placeholder for repository-wide settings, allowing automated reviewer assignment to function without complex dependencies.