yeet

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/alexaundre/mycc --skill yeet-alexaundre
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/alexaundre/mycc/tree/main/.codex/skills/yeet
Command: npx skills add https://github.com/alexaundre/mycc --skill yeet-alexaundre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the repetitive, error-prone steps required to prepare a local git change for review by staging changes, creating a focused commit, pushing a branch, and opening a GitHub pull request in a single flow.

Core Features & Use Cases

  • Pre-flight checks: Verifies the GitHub CLI is installed and that the user is authenticated before proceeding.
  • Branching and naming: Creates a codex/{description} branch when starting from main and enforces concise commit and PR title conventions.
  • End-to-end flow: Stages all changes, commits with a terse message, pushes with tracking, retries common push failures, and opens a draft PR with a populated title and body.
  • Use Case: A developer who has finished a focused change and wants to quickly stage, commit, push, and open a draft PR using the GitHub CLI.

Quick Start

Prepare this branch for review by staging all changes, committing with a concise description, pushing to origin, and opening a draft pull request 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?▼

You can automate staging, committing, and opening a GitHub pull request by using a single-flow CLI workflow that stages all changes, commits with a concise message, pushes the branch, and opens a draft PR via the GitHub CLI.

What do I need to create a pull request from my local git branch using the GitHub CLI?▼

To create a pull request using the GitHub CLI, you need the CLI installed and authenticated, a git workspace with pending changes, and adherence to branch, commit, and PR naming conventions.

How does the branch naming convention work when creating a PR from main?▼

When creating a PR from the main branch, the workflow automatically creates a codex/{description} branch, stages your changes, and pushes with tracking before opening the draft pull request.

What happens if pushing my local git branch to origin fails during PR creation?▼

If pushing your local git branch to origin fails during PR creation, the workflow automatically retries common push failures before proceeding to open the draft pull request.

Can I push code and open a draft PR without manually writing separate git commit commands?▼

Yes, you can push code and open a draft PR without separate git commit commands by running an end-to-end flow that stages all working changes, commits with a terse message, pushes to origin, and opens the draft PR.

Are there limitations to automating pull request creation with the GitHub CLI?▼

Limitations of automating pull request creation include requiring explicit user requests for single-flow PR creation, strict adherence to concise commit and PR title conventions, and a pre-flight check to verify the GitHub CLI is installed and authenticated.