r2r init

Creates a minimal .r2r/r2r-cli.yml configuration file in the repository root. This is the first step in setting up R2R for extension management.

Syntax

r2r init [flags]

Description

The init command creates the .r2r/r2r-cli.yml file in your project. This file manages extension registration and configuration.

What it does:

Creates the .r2r/ directory if needed
Generates a minimal r2r-cli.yml with empty extension list
Ready for extension installation via r2r install

What it creates:

extensions: []

Flags

Flag	Description
`--delete-configs`	Delete all configuration files including overrides
`--use-pwd-as-root`	Use current directory as repository root (creates .git if needed)
`-h, --help`	Display help information

Examples

Basic Initialization

cd /path/to/your/project
r2r init

Reset Configuration

Remove all existing configuration and start fresh:

r2r init --delete-configs

Three-Step Setup

# Step 1: Initialize R2R configuration
r2r init

# Step 2: Install EAC extension
r2r install eac

# Step 3: Configure EAC
r2r eac init --ai-provider claude-api

File Structure

After r2r init:

your-project/
├── .r2r/
│   └── r2r-cli.yml      # Extension registry (empty)
└── (your project files)

After r2r install eac:

your-project/
├── .r2r/
│   └── r2r-cli.yml      # Contains eac extension
└── (your project files)

After r2r eac init:

your-project/
├── .r2r/
│   ├── r2r-cli.yml          # Extension registry
│   └── eac/                 # EAC configuration
│       ├── ai-provider.yml
│       └── repository.yml
└── (your project files)

Configuration File

The generated configuration:

# Empty configuration - extensions added via 'r2r install'
extensions: []

After installing EAC:

extensions:
  - name: 'eac'
    image: 'ghcr.io/ready-to-release/ext-eac:latest'
    description: 'Everything-as-Code automation'