yeet

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

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Estom/aiflex --skill yeet-estom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/openai-skills/yeet
Command: npx skills add https://github.com/Estom/aiflex --skill yeet-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the multi-step Git workflow of staging changes, creating a concise commit, pushing a branch, and opening a GitHub pull request so users can create review-ready PRs quickly and consistently.

Core Features & Use Cases

  • Single-flow PR creation: Coordinates branch creation, staging, committing, pushing, and PR opening using the GitHub CLI.
  • Consistency and conventions: Enforces branch and commit naming conventions (branch: codex/{description}, commit: {description}, PR title: [codex] {description}).
  • Use Case: Ideal for developers who want an automated, repeatable flow to prepare and open a draft PR after making a focused change without manually running each Git and gh command.

Quick Start

Run the yeet skill to stage all changes, commit with a terse description, push the branch with tracking, and open a draft PR via the GitHub CLI.

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 step?

To automate staging, committing, and opening a GitHub pull request in one step, use a single-flow workflow that stages all changes, commits with a brief message, pushes the branch with tracking, and opens a draft PR via the GitHub CLI. This ensures review-ready PRs are created quickly and consistently.

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

Yes, automating git commit and pull request creation requires the GitHub CLI to be installed and authenticated. The single-flow PR creation process relies on the gh command to push the branch with tracking and open the draft pull request on your behalf.

What branch naming convention is enforced when automating a git commit and PR flow?

Automating a git commit and PR flow enforces a strict branch naming convention of codex/{description}. This consistency applies to the commit message format as well, ensuring the branch, commit, and draft PR title all align with the specified description.

Can I push a branch and create a draft PR without manually running multiple git commands?

Yes, you can push a branch and create a draft PR without manually running multiple git commands by using an automated single-flow process. It handles staging all changes, committing with a terse description, pushing with tracking, and opening the draft pull request through the GitHub CLI.

What is the best way to create review-ready GitHub pull requests for focused code changes?

The best way to create review-ready GitHub pull requests for focused code changes is to use an automated workflow that stages all changes, commits, pushes the branch with tracking, and opens a draft PR. This eliminates manual Git and gh commands while enforcing consistent branch and commit conventions.