git-commit

Automate git commits by delegating repository status checks, diff reviews, and selective staging to a Bash subagent. The workflow generates conventional commit messages for code changes while keeping the main context clean and returning a final summary.

Yes, you can selectively stage files for a git commit while skipping sensitive items. The workflow inspects repository status and diffs first, ensuring only safe, intended code changes and configuration updates are staged before generating the commit message.

Automated git commit workflows include error handling for pre-commit hooks. If a hook fails during the commit process, the Bash subagent catches the error to prevent broken commits and maintain safe version-control practices.

The best way to push git commits safely is using an optional push confirmation step. After generating a conventional commit message and staging files, the workflow prompts for confirmation before pushing changes to the remote repository.

Yes, a Bash subagent is required to automate git status inspection and diff review. Delegating all repository changes to Bash ensures that git operations execute correctly while keeping the main assistant context focused on outcomes.

Using a subagent for git commit automation keeps the main context clean by isolating verbose git command outputs. It ensures a clear, final summary of staged changes and conventional commit messages is returned without cluttering the conversation.