github-pr-create-update

Creates or updates a GitHub pull request from the current branch to origin/development.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/CareCard-ca/pkg-auth-util --skill github-pr-create-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-create-update
Source: https://github.com/CareCard-ca/pkg-auth-util/tree/main/.agents/skills/github-pr-create-update
Command: npx skills add https://github.com/CareCard-ca/pkg-auth-util --skill github-pr-create-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents stalled or inconsistent remote pull requests by standardizing how to push your current branch and either create a new GitHub PR or update an existing one against the latest development baseline.

Core Features & Use Cases

  • GitHub PR create/update: Creates a PR from the current committed branch into development, or reuses an existing open PR for the same branch.
  • Development synchronization: Fetches and validates against the latest origin/development to reduce surprises and detect merge-tree conflicts early.
  • Draft readiness handling: Marks the PR ready when the existing PR is currently a draft, then updates the PR title to be descriptive and non-draft.

Quick Start

Use this skill when you explicitly ask to push your current branch and create or update the corresponding GitHub pull request from that branch into development.

Frequently Asked Questions about github-pr-create-update

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

FAQPage Schema
How do I create a pull request from my current branch into development using GitHub CLI?

To create a pull request, this skill pushes your current committed branch and uses authenticated GitHub CLI to open a PR against origin/development after validating merge compatibility.

Can I update an existing GitHub pull request and mark it ready for review?

Yes, you can update an existing GitHub pull request by reusing the open PR for your branch, marking it ready if it is a draft, and modifying the title to remove draft wording.

Does this GitHub PR workflow check for merge conflicts before pushing?

Yes, the PR creation workflow fetches the latest origin/development and validates merge tree compatibility early to detect conflicts before you push your branch.

What is the best way to safely push a local git branch to a remote GitHub PR?

The safest way to push a remote GitHub PR is to apply strict remote operation guardrails, perform preflight worktree checks, and rebase as needed to ensure the PR reflects intended committed changes.

Do I need GitHub CLI authentication to create or update a pull request?

Yes, authenticated GitHub CLI usage is required to execute remote pull request operations, ensuring secure and authorized branch pushing and PR management against development.

Why does my pull request creation fail when my local branch is out of sync?

Pull request creation fails when out of sync because the skill requires fetching the latest development reference and validating merge compatibility to ensure your committed changes apply cleanly.