push

Push local git branches and manage pull requests on GitHub.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/zhaozengqing4364-bit/sales-training-qoder --skill push-zhaozengqing4364-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/zhaozengqing4364-bit/sales-training-qoder/tree/main/.codex/skills/push
Command: npx skills add https://github.com/zhaozengqing4364-bit/sales-training-qoder --skill push-zhaozengqing4364-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of pushing code changes and managing pull requests on GitHub, reducing manual effort and the risk of errors during collaboration.

Core Features & Use Cases

  • Automated Branch Push: Push local commits to remote repositories with upstream tracking.
  • PR Management: Create and update pull requests based on branch differences and project status.
  • Use Case: A developer has completed a feature branch and wants to push their changes and open a PR seamlessly, ensuring all validation and review steps are followed.

Quick Start

Use the push skill to push your current branch and automatically open or update the pull request on GitHub.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate pushing a local git branch and creating a GitHub pull request?

Automating git branch pushing and pull request creation streamlines code review workflows. The Skill handles upstream tracking, branch differences validation, and PR operations, ensuring consistent collaboration and reducing manual effort when opening or updating pull requests on GitHub.

Do I need GitHub CLI installed to automate pull request creation?

Yes, GitHub CLI is required to automate pull request creation. The Skill relies on both Git and GitHub CLI tools to perform validation, push local commits to remote repositories, and reliably manage pull request operations on GitHub.

What's the best way to maintain consistent code review workflows for feature branches?

Maintaining consistent code review workflows requires automated branch pushing and PR management. This Skill standardizes the process by validating branch differences and project status before pushing local commits and opening or updating GitHub pull requests.

How does automated PR management handle updating existing pull requests?

Automated PR management handles updating existing pull requests by evaluating branch differences and current project status. It pushes local commits with upstream tracking and adjusts the pull request on GitHub, ensuring the review process reflects the latest changes.

Can I use this automation to push commits with upstream tracking for remote repositories?

Yes, you can use this automation to push commits with upstream tracking. It streamlines Git workflows by automatically pushing local commits to remote repositories while setting up upstream tracking, which is essential for maintaining reliable branch synchronization.

Are there limitations when automating GitHub pull requests across different repository statuses?

Automating GitHub pull requests depends on accurate branch difference validation and project status checks. Limitations arise if Git or GitHub CLI tools are missing, as reliable push and PR operations require these dependencies to properly validate and manage the code review workflow.