yeet

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

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/syl2042/codex_skills --skill yeet-syl2042
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/syl2042/codex_skills/tree/main/yeet
Command: npx skills add https://github.com/syl2042/codex_skills --skill yeet-syl2042

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated Git workflows are repetitive and error-prone; this skill automates staging, committing, pushing, and opening PRs to ensure consistent changelist preparation.

Core Features & Use Cases

  • End-to-end Git flow orchestration: create a branch, stage changes, commit with a concise message, push to origin, and open a PR with a descriptive title.
  • PR housekeeping: ensures a clean, review-ready branch for team collaboration.
  • Use Case: A developer wants to push a small fix and open a PR in one go, minimizing context-switching and manual steps.

Quick Start

Run the full Yeet flow to stage changes, commit with a concise message, push to origin, and open a PR via 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?

Automating the end-to-end Git workflow lets you stage, commit, push, and open a pull request in one flow. This skill orchestrates branch creation, staging, and PR creation using the GitHub CLI to ensure consistent changelist preparation.

What is the best way to automate a Git commit and push a feature branch?

The best way to automate a Git commit and push is by orchestrating the end-to-end flow. The skill handles branch creation, stages your changes, commits with a concise message, and pushes to origin automatically, minimizing manual steps and context-switching.

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

Yes, you need the GitHub CLI installed and authenticated to automate pull request creation. The skill requires a Git repository with gh configured to push branches to origin and open review-ready PRs in sequence.

Why does my automated Git workflow need branch creation before opening a PR?

Automated Git workflows need branch creation before opening a PR to isolate changes for team collaboration. Creating a clean, review-ready branch ensures your staged changes are properly pushed to origin before the pull request is generated.

Can I use this to push a small fix and open a PR without manual steps?

Yes, you can push a small fix and open a PR without manual steps. The skill coordinates the entire Git flow, staging changes and committing with a descriptive title, which is ideal for developers wanting to minimize context-switching.