push

Push Git branches to origin and create or update GitHub pull requests.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/airhorns/jam --skill push-airhorns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/airhorns/jam/tree/main/.agents/skills/push
Command: npx skills add https://github.com/airhorns/jam --skill push-airhorns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push and PR management are manual, error-prone, and slow; this Skill automates syncing a local feature branch with origin and ensures a corresponding pull request exists or is updated, reducing context switching.

Core Features & Use Cases

  • Push the current branch to origin with upstream tracking when needed and verify remote state before pushing.
  • Create a new pull request if none exists, or update an existing one when the branch changes.
  • Handle non-fast-forward or merge conflicts by prompting a pull of origin/main and revalidating before retrying the push.
  • Ensure PR bodies reflect the latest scope using a template, and surface exact errors for auth or workflow restrictions.

Quick Start

Use the push skill to push your current feature branch and create or update the corresponding PR on GitHub.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automatically push a Git branch and create a pull request at the same time?

To push a Git branch and create a pull request simultaneously, the Skill verifies the remote state, pushes the current branch to origin with upstream tracking, and auto-creates or updates the corresponding PR using validated templates.

What happens when a non-fast-forward error occurs during a Git push?

When a non-fast-forward error occurs during a Git push, the Skill prompts you to pull from origin/main, revalidates the branch state, and retries the push to resolve merge conflicts safely.

Do I need the GitHub CLI to automate branch management and PR updates?

Yes, you need the GitHub CLI (gh) to automate branch management and PR updates, along with a configured repository, upstream tracking, and PR templating to validate titles and bodies.

How does auto-updating an existing pull request work when a branch changes?

Auto-updating an existing pull request works by detecting branch changes, pushing the updates to origin, and modifying the PR body to reflect the latest scope using a predefined template.

Can I use this automation for collaborative software engineering workflows with feature branches?

Yes, you can use this automation for collaborative software engineering workflows because it safely syncs local feature branches with origin, manages pull requests, and handles auth or workflow restriction errors.

Why does my pull request body need to match a specific template?

Your pull request body needs to match a specific template to ensure PR bodies reflect the latest scope accurately, validate PR titles, and surface exact errors for workflow restrictions during the automated creation process.