playbooks

home / skills / openai / skills / yeet

yeet skill

/skills/.curated/yeet

This skill orchestrates staging, committing, pushing, and PR creation via gh in one fluent flow for Git workflows.

npx playbooks add skill openai/skills --skill yeet

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
1.7 KB
---
name: "yeet"
description: "Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`)."
---

## Prerequisites

- Require GitHub CLI `gh`. Check `gh --version`. If missing, ask the user to install `gh` and stop.
- Require authenticated `gh` session. Run `gh auth status`. If not authenticated, ask the user to run `gh auth login` (and re-run `gh auth status`) before continuing.

## Naming conventions

- Branch: `codex/{description}` when starting from main/master/default.
- Commit: `{description}` (terse).
- PR title: `[codex] {description}` summarizing the full diff.

## Workflow

- If on main/master/default, create a branch: `git checkout -b "codex/{description}"`
- Otherwise stay on the current branch.
- Confirm status, then stage everything: `git status -sb` then `git add -A`.
- Commit tersely with the description: `git commit -m "{description}"`
- Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
- Push with tracking: `git push -u origin $(git branch --show-current)`
- If git push fails due to workflow auth errors, pull from master and retry the push.
- Open a PR and edit title/body to reflect the description and the deltas: `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)`
- Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \\n-escaped markdown.
- PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

Overview

This skill automates a single flow to stage, commit, push, and open a GitHub pull request using the GitHub CLI (gh). It enforces repository conventions for branch names, commit messages, and PR content so changes are consistent and review-ready. Use it only when you explicitly ask to perform the full staging-to-PR flow in one command sequence.

How this skill works

The skill first verifies that the GitHub CLI is installed and that the user is authenticated with gh. It creates a codex-style branch when starting from the default branch, stages all changes, makes a terse commit, runs checks, pushes the branch with tracking, and opens a draft pull request via gh. The PR body is composed as real markdown with full newlines and detailed prose describing the issue, root cause, fix, and validation steps.

When to use it

  • You want to stage, commit, push, and open a PR in one uninterrupted flow.
  • You have gh installed and authenticated (gh auth status returns OK).
  • You accept the repository branch/commit/PR naming conventions used by the skill.
  • You want the PR created as a draft with a detailed markdown description.
  • You are ready for the workflow to run checks and possibly install missing dev deps.

Best practices

  • Ensure gh is installed (gh --version) and authenticated (gh auth status) before requesting the flow.
  • Provide a concise description to use for branch name, commit message, and PR title.
  • Run local tests or linters first to reduce iteration on failing checks after commit.
  • If on main/master/default, allow the skill to create a branch named codex/{description}; otherwise confirm staying on the current branch.
  • Edit the generated PR body to add any extra context or bespoke testing steps before marking it ready for review.

Example use cases

  • You finished a small bug fix and want one command to stage changes, commit with a terse message, push, and open a draft PR.
  • You implemented a feature on main and need a properly named codex branch and a filled PR with the required description template.
  • You want to push exploratory changes and collect reviewer feedback using a draft PR created via gh.
  • You need to re-run checks, install missing dev dependencies, and then push and open a PR in a single guided flow.

FAQ

What if gh is not installed or I am not authenticated?

The skill will stop and prompt you to install gh (gh --version) or run gh auth login, and to re-run gh auth status before continuing.

How are branch names, commits, and PR titles formed?

Branches follow codex/{description} when starting from default; commits use the terse description; PR titles use the pattern [codex] {description} and the body is detailed markdown covering issue, root cause, fix, and validation.