What problem does it solve? Publishing local commits to a shared remote branch is error-prone in multi-agent or multi-collaborator environments: pushes get rejected by non-fast-forward races, force-push flags destroy history, and silent failures leave work unpublished. This Skill performs only the safe push step, with guardrails against dangerous flags and a defined recovery path. ## Core Features & Use Cases - Idempotent push check: Counts commits ahead of and behind the remote before pushing, exiting cleanly as a no-op when there is nothing to publish. - Footgun refusal: Rejects any request containing --force, --force-with-lease, --no-verify, or --no-gpg-sign flags before running anything. - Race recovery: On a non-fast-forward rejection, fetches, rebases onto the remote branch, and retries the push exactly once, then stops and surfaces the state if it still fails. - Stuck-state logging: Appends structured failure entries to a memory file so a coordinating agent can pause dispatches and escalate until the blockage resolves. - Use Case: An autonomous coding agent finishes committing a bug fix locally and asks to publish the work; the Skill verifies there are commits to push, pushes to origin, handles a sibling agent's concurrent push via rebase, and confirms the local and remote branches match. ## Quick Start Push my local commits to the remote default branch and let me know if anything gets stuck.
