git-workflow-automation

Enforce conventional commits by automating a 2-commit strategy per task, generating standardized messages with appropriate scope and type to maintain a predictable Git history. This prevents merge conflicts through automated preflight checks.

A 2-commit strategy guarantees one feature commit and one documentation commit per task. This phase-based approach separates implementation from documentation to standardize Git workflow management and ensure a clean history.

Automate preflight environment validation by running setup scripts to verify tooling like nvm, git, and yarn. This checks branch state and dependencies before work begins, ensuring a safer development environment.

Yes, generate conventional commit messages from a task plan file like 03_plan.md. By passing the task identifier to a generator script, the system outputs standardized commit messages for your feature and documentation commits.

The best way to prevent merge conflicts is executing preflight checks and safer operations before committing. Automated workflow management validates branch state and dependencies, providing clear rollback guidance during conflicts.

If a phase-based Git commit sequence fails, follow the provided progress reporting and safe recovery guidance. The workflow validates the commit sequence and offers clear rollback instructions to safely recover during conflicts.