aster-fix-workflow

name	aster-fix-workflow
description	Pipe aster review findings into aster fix to generate and apply patches safely, using review --json, fix --findings-json, dry-run inspection, --apply, and permission gating. Use when asked to auto-fix review findings, apply aster's suggested edits, or build a review-then-fix pipeline.

Review → fix workflow

aster fix takes findings produced by aster review --json and asks the model for concrete edits. It is dry-run by default and only writes with --apply, subject to the permissions block in aster.yaml.

The pipeline

aster review --json > findings.json        # 1. review, capture findings
aster fix --findings-json findings.json    # 2. dry-run: preview proposed edits
aster fix --findings-json findings.json --apply   # 3. write to the working tree

Or as one stream:

aster review --json | aster fix --findings-json - --apply

Rules

• ALWAYS run the dry-run first and read the preview before --apply. Never jump straight to --apply on findings you have not seen.
• --apply writes to the working tree only; it never commits. Review the diff with git diff afterward and commit yourself.
• Writes are gated by permissions in aster.yaml (mode, plus allow/ask/deny rules). A headless run has no way to answer a prompt, so anything that reaches ask is refused: automation needs mode: edit with explicit allow rules like .