Overview

🚀Initialize Reflow

Recommended

Create project-owned Reflow configuration in a persistent local target without changing Git history or remote state.

Commandreflow init

📦Category

Initialization

🚀Quick Command

reflow init [OPTIONS]

---

configurationlocal targetproject setup

---

📁

Target

Persistent local directory

⚙️

Generated Path

.config/reflow/config.toml

🌿

Git History

Not changed

✅

Dry-run

No filesystem mutation

What This Command Does

✨Features

📁Resolve a Local Target

Use the current directory or an explicit -C/--repository path. Repository URLs are rejected.

⚙️Plan Configuration Resources

Resolve the supported all or config mode and show the selected project resource.

🛡️Protect Existing Content

Preserve an existing project-owned file unless overwrite behavior is explicitly approved.

✅Report the Result

Show created, skipped, failed, or simulated resources and the resolved mode.

⚠️Safety boundary

Live mode writes only the selected initialization resource. Dry-run does not create directories, write or replace files, or request overwrite confirmation. The command never creates commits, tags, pushes, releases, or registry images.

ℹ️Supported modes in Reflow 1.0.2

The public CLI accepts all and config. Both currently prepare the Reflow configuration workspace; values such as templates, examples, and all_no_examples are not accepted by the active InitMode enum.

🚀Related Commands

Commands commonly used together with this command.

Options

Choose a supported mode and overwrite policy.

Workflow

Follow planning, dry-run, and file-write stages.

Configuration

Understand initialization defaults and ownership.