Overview

🚀Reflow Developer Guide

Contributor Guide

Change repository-aware release workflows without weakening targeting, dry-run, or mutation safeguards.

Commandmake check

📦Category

Development

🚀Quick Command

setup -> focused change -> widening validation

---

Python 3.14+pytestpre-commitrelease safety

---

Contributor priorities

Reflow can replace Git tag names, re-push remote tags, and publish container images. Contributor work must keep repository selection explicit, previews accurate, dry-run non-mutating, and external operations outside ordinary test runs.

✨Development Boundaries

💻CLI

Keep Typer parsing, prompts, help, and Rich presentation under app/cli.

🏗️Core Workflows

Keep reusable Git, repository, conversion, recovery, Docker, and initialization behavior under app/core or its service layer.

⚙️Configuration

Preserve CLI → configuration → default precedence and keep packaged templates synchronized with supported fields.

🛡️Safety

Test local, remote, confirmation, failure, and dry-run boundaries independently; never use production remotes or registries for routine validation.

---

Quality workflow

Install the editable development environment, enable the repository hook, run the smallest affected test first, then run formatting, lint, and the complete suite before handoff.

ℹ️Pre-commit complements full validation

The hook catches common formatting, lint, whitespace, and newline problems on the files being committed. It does not replace Reflow's complete pytest suite, dry-run regression coverage, or applicable container and documentation checks.

---

🚀Related Commands

Commands commonly used together with this command.

Development Setup

Install Reflow and contributor tools in an isolated environment.

Testing

Choose focused tests and run complete quality gates.

Contributing

Prepare a focused and reviewable Reflow change.

Architecture

Trace Reflow's application layers and workflow boundaries.