yeet

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

2|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Sacred-G/oh-my-claw --skill yeet-sacred-g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/Sacred-G/oh-my-claw/tree/main/secure-openclaw/skills-main/skills/.curated/yeet
Command: npx skills add https://github.com/Sacred-G/oh-my-claw --skill yeet-sacred-g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines Git workflow by staging changes, committing with a concise message, pushing to the active branch, and opening a pull request in a single, automated flow using the GitHub CLI.

Core Features & Use Cases

  • Automates end-to-end git operations: stage, commit, push, and PR creation.
  • Supports authenticated GitHub CLI (gh) sessions and standard branch naming conventions.
  • Use case: a developer finishes a small feature, runs a single command flow to submit a PR for review.

Quick Start

Stage all changes, commit with a concise message, push to the branch, and open a pull request using gh.

Frequently Asked Questions about yeet

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

FAQPage Schema
How do I automate staging, committing, and opening a GitHub pull request in one flow?

You can automate staging, committing, pushing, and opening a GitHub pull request in a single flow using the GitHub CLI. This requires an authenticated gh session and a configured repository to execute the end-to-end git operations automatically.

What is the best way to streamline git workflow for feature branches and PR submissions?

Streamlining git workflow for feature branches involves automating the sequence of staging, committing, pushing, and PR creation. Using the GitHub CLI provides a fast, repeatable workflow that submits your feature branch for review in a single command flow.

Do I need GitHub CLI authentication to automate commit and pull request creation?

Yes, GitHub CLI authentication is required to automate commit and pull request creation. The workflow relies on an authenticated gh session and standard branch naming conventions to push changes and open a pull request on your configured repository.

Can I use this automated git workflow for small features on a configured repository?

You can use this automated git workflow for small features on a configured repository. It is designed for developers who want a fast, repeatable workflow to stage changes, commit with a concise message, push, and submit a PR for review.

Are there limitations when pushing changes and opening a pull request using the GitHub CLI?

Limitations when pushing changes and opening a pull request using the GitHub CLI include the strict requirement for an authenticated gh session and a properly configured repository. You must also adhere to standard branch naming conventions for the automated PR creation to succeed.