git-workflow

Automating git commits and pull requests for multi-file changes involves analyzing scope to categorize files, enforcing Conventional Commits formatting, and orchestrating direct or agent-based commits. This workflow optionally pushes branches and creates PRs via MCP tools or GitHub CLI.

Keeping documentation updates synchronized with code commits is achieved by coordinating parallel docs-git-committer agents for larger changes. This approach analyzes code, docs, and config scope to generate commits that maintain documentation alignment alongside feature updates.

Enforcing Conventional Commits formatting automatically requires a workflow that analyzes staged changes and generates compliant commit messages. It categorizes files across features, docs, and tests to determine the correct commit type and scope before finalizing the commit.

Yes, this git workflow automation works with the GitHub CLI for PR creation. After committing changes, it optionally pushes the branch and generates pull requests directly through GitHub CLI or MCP tools to streamline release workflows.

Direct commits should be used for small changes, while agent-based commits are better for larger, multi-file changes. The workflow analyzes the scope of code, docs, and config modifications to automatically decide the optimal commit path.

You need GitHub CLI installed to create pull requests via CLI, or you can use MCP tools as an alternative. The workflow relies on these dependencies to push branches and generate PRs after orchestrating your commits.