yeet

Stage changes, commit, push, and open a GitHub pull request via gh.

2|1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/duggal1/Sapphire-cli --skill yeet-duggal1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/duggal1/Sapphire-cli/tree/main/internal/skills/bundled/yeet
Command: npx skills add https://github.com/duggal1/Sapphire-cli --skill yeet-duggal1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates a multi-step Git workflow to stage changes, commit with a concise message, push the branch, and open a GitHub pull request using the GitHub CLI (gh), reducing overhead and errors in code collaboration.

Core Features & Use Cases

  • Automates end-to-end Git operations: stage, commit with a clear message, push, and create a PR with a standardized title.
  • Enforces prechecks: verifies gh is installed and authenticated before continuing.
  • Handles collaborative workflows: suitable for team code reviews and PR-driven releases.

Quick Start

Stage changes, commit with a concise message, push the branch, and open a PR using gh in one seamless flow.

Frequently Asked Questions about yeet

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

FAQPage Schema
How do I automate a git workflow to stage, commit, push, and open a pull request in one step?

You can automate staging, committing, pushing, and opening a GitHub pull request in one flow using this Skill. It chains these git operations together, applying a concise commit message and standardized PR title to reduce manual overhead and errors in collaborative development.

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

Yes, you need the GitHub CLI (gh) installed and authenticated to automate pull request creation. This Skill performs prerequisite checks to verify gh availability and authentication before proceeding with the automated branch push and PR generation.

Can I enforce standardized PR titles and branch naming conventions for team code reviews?

Yes, you can enforce standardized PR titles and branch naming conventions for team code reviews. This Skill applies branch naming conventions and generates a standardized PR title, satisfying functional requirements for repeatable, PR-driven releases across collaborative branches.

What is the best way to reduce manual errors when pushing code changes across branches?

The best way to reduce manual errors when pushing code changes is to automate the multi-step git workflow. This Skill provides a repeatable, single-flow operation that stages changes, commits, pushes, and opens a PR, eliminating manual command sequencing mistakes.

Does this automated commit and PR workflow work for collaborative software development?

Yes, this automated commit and PR workflow works for collaborative software development where teams require repeatable operations. It is specifically designed for team code reviews and PR-driven releases, handling end-to-end Git operations across branches.