What problem does it solve? It enforces a controlled, confirmation-based Git commit and push workflow that only touches explicitly planned files, preventing accidental commits of unrelated dirty changes and keeping task progress records in sync. ## Core Features & Use Cases - Exact-file commits: Builds a minimal plan of exact files per repository, confirms once with the user, then commits and pushes only those files without using git add . or git add -A. - Multi-repo execution chains: Discovers candidate repositories from .trellis/ config, supports deterministic local generation commands between repos, and stops safely on drift or failure without rolling back successful commits. - Task progress synchronization: After successful business pushes, atomically writes final progress and completion state via task_progress.py, then commits and pushes the task record as a separate exact-file commit. - Use Case: After finishing a feature spanning two packages in a monorepo, run the push phase to confirm a single plan, commit each repo's planned files, push both branches, and mark the active task completed in one controlled flow. ## Quick Start Ask the assistant to commit and push the current task's changes using the trellis-push workflow and confirm the displayed plan.
