commit-push

Automating git commit and push with branch naming conventions involves validating the current branch against protected branches like main, master, dev, and rc* patterns, then automatically creating or renaming branches to match feat/* or hotfix/* rules before pushing. This ensures compliant branch execution without manual checks.

When committing to a protected git branch like main or master, the workflow detects the violation and automatically creates or renames a compliant branch based on your naming conventions, ensuring changes are redirected to an approved branch before the push executes.

You can override default branch validation rules by defining project-specific adjustments in local override files such as .claude/be-harness/common.md, allowing you to adapt branch naming patterns and pre-commit checks before the automated push executes.

The best way to preview branch changes before an automated git push is to trigger the commit workflow, which stages pre-commit checks and branch validation steps, letting you review logical commit units and branch compliance before the push is applied.

No, this automated git commit workflow requires no external dependencies, operating entirely through deterministic pre-commit checks, branch validation, and push execution while reading local project overrides to adapt rules as needed.

An automated git push may fail if the custom branch naming pattern does not match defined conventions like feat/* or hotfix/*, triggering branch validation errors that require creating or renaming the branch to satisfy compliance rules before pushing.