agent-git-push-workflow

Automating git commit and push for mesh agents requires configuring SSH keys for repository access. This skill facilitates autonomous SSH commit pushes to canonical repositories, eliminating human intervention by streamlining git cloning and push semantics.

Setting up SSH for automated git pushes involves a one-time configuration to establish git clone and push aliases for direct access. This skill provides the necessary setup scripts to enable SSH keys, ensuring routine changes are processed automatically without manual authentication.

Direct git push to main does not work for collaborative code reviews. While the skill defaults to direct pushes to the main branch for autonomous changes, it offers a PR workflow specifically for collaborative reviews and atomic changes when needed.

Structuring commit messages for autonomous repository management requires following specific commit message standards. This skill provides guidelines for structured commit messages, improving traceability and collaboration across mesh agents pushing directly to canonical repositories.

Yes, you need SSH keys to push commits directly to MCERQUA repositories. The skill relies on SSH for secure authentication and requires both git and ssh dependencies to enable autonomous deployment and direct-push access for mesh agents.