push

Publish verified local commits to a remote Git branch with pre-push validation.

16|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/hojinzs/github-symphony --skill push-hojinzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/hojinzs/github-symphony/tree/main/.codex/skills/push
Command: npx skills add https://github.com/hojinzs/github-symphony --skill push-hojinzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing local commits to a remote branch often risks unsafe force pushes and cluttered history. This Skill provides a safe, auditable workflow that ensures commits are pushed correctly with validation and fallback when conflicts arise.

Core Features & Use Cases

  • Pre-push validation: Runs tests and lint checks before pushing to catch issues early.
  • Non-fast-forward handling: Automatically fetches and merges when needed, with conflict resolution guidance.
  • Guardrails: Prevents pushing directly to protected branches like main or master; records outcomes to the workpad.

Quick Start

Push verified local commits to the remote branch using the standard safe-push flow.

Frequently Asked Questions about push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely push git commits to a remote branch without force pushing?

To safely push git commits, this workflow applies pre-push validation and publishes verified local commits to a remote branch while strictly avoiding unsafe force pushes. It enforces guardrails to prevent direct pushes to protected branches like main or master.

What is the best way to handle non-fast-forward errors when pushing to origin?

Handling non-fast-forward errors requires fetching and merging remote changes before retrying the push. This workflow automatically fetches and merges when needed, providing conflict resolution guidance to ensure your local commits are published correctly without cluttering history.

Does this git workflow run checks before pushing to the remote repository?

Yes, this git workflow runs pre-push validation by executing tests and lint checks before pushing to the remote repository. These automated checks catch issues early to ensure only verified local commits are published to the origin branch.

How can I prevent accidental direct pushes to main or master branches?

You can prevent accidental direct pushes using built-in guardrails that block publishing commits directly to protected branches like main or master. This ensures your standard Git workflow across feature branches remains safe and auditable.

What happens when git push conflicts occur during branch management?

When git push conflicts occur, the workflow automatically fetches and merges the remote branch, providing conflict resolution guidance. This non-fast-forward handling ensures local commits are safely reconciled with the remote branch before completing the push.