push-pr

Push the current branch to origin and create a PR to upstream.

84|11|Updated Feb 14, 2025
One-click install
npx skills add https://github.com/Positronic-Robotics/positronic --skill push-pr-positronic-robotics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push-pr
Source: https://github.com/Positronic-Robotics/positronic/tree/main/.claude/skills/push-pr
Command: npx skills add https://github.com/Positronic-Robotics/positronic --skill push-pr-positronic-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the workflow of pushing the current development branch to origin and opening a PR to upstream, ensuring any uncommitted changes are addressed before pushing.

Core Features & Use Cases

  • Check for uncommitted changes and prompt to commit before pushing
  • Push to origin and create a PR to upstream using GitHub CLI
  • Enforce basic commit-message guidance and PR metadata to standardize contributions

Quick Start

Review your working tree, commit any changes if needed, then push the branch and create the PR to upstream

Frequently Asked Questions about push-pr

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

FAQPage Schema
How do I automate pushing a git branch to origin and opening a pull request?

This Skill automates the workflow by checking for uncommitted changes, using git push -u origin HEAD, and invoking gh pr create with a base of main to open a pull request to upstream.

What happens to uncommitted changes when I try to push my current branch?

The workflow checks for uncommitted changes and prompts you to commit them before pushing, ensuring your working tree is clean before opening a pull request.

Can I create a pull request to upstream using GitHub CLI from a fork?

Yes, the workflow uses gh pr create with a base of main and a head referencing your branch, specifically designed for collaborative development workflows using forks.

What's the best way to standardize pull request metadata and commit messages for code review?

The workflow enforces basic commit-message guidance and standardizes PR metadata, aligning with your project's conventions to ensure consistent contributions before merging into the main repository.

Does this pull request automation work with feature branches and forks?

Yes, the automation is specifically applied to collaborative software development workflows using forks and feature branches, ensuring changes are validated before contributing to the main repository.