Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/openai/skills/llms.txt

Use this file to discover all available pages before exploring further.

The yeet skill compresses the entire “I’m done coding, time to open a PR” sequence into a single Codex prompt. It stages your changes, writes a terse commit message, pushes to a tracking branch, discovers and applies your repository’s PR template (if one exists), and opens a well-structured draft pull request — all through the GitHub CLI (gh). What normally takes several terminal commands and careful copy-pasting happens in one coherent, reviewable flow.

​
Trigger conditions

yeet activates only when you explicitly ask to publish changes as a pull request. Common triggers include:
  • “Yeet this”
  • “Open a PR for these changes”
  • “Stage, commit, and push — open a draft PR”
  • “Prepare this branch for review”
This skill requires both the GitHub CLI (gh) and an authenticated gh session. Codex will check for both prerequisites and stop with clear instructions if either is missing.

​
Prerequisites

1

Install the GitHub CLI

Follow the instructions at cli.github.com for your platform, then confirm the install:
gh --version
2

Authenticate

gh auth login
gh auth status

​
Workflow

Once prerequisites are confirmed, yeet runs through the following steps automatically:
1

Branch

If you are on main, master, or the default branch, a new branch is created using your change description as the name. If you are already on a feature branch, the skill stays put.
2

Stage and commit

Runs git status -sb to confirm what is changing, then git add -A to stage everything. Commits with a terse message describing the change.
3

Run checks

If pre-push checks are configured and have not yet run, the skill runs them. If they fail due to missing dependencies, it installs deps and retries once.
4

Push

Pushes with upstream tracking: git push -u origin <current-branch>. If the push fails due to workflow auth errors, it pulls from the default branch and retries.
5

Discover PR template

Searches for an active GitHub PR template in this order:
  • .github/pull_request_template.md
  • .github/PULL_REQUEST_TEMPLATE.md
  • A single *.md file under .github/pull_request_template/
  • A single *.md file under .github/PULL_REQUEST_TEMPLATE/
If exactly one template is found it is read and passed to gh pr create --template. If multiple are found, Codex pauses and asks which to use.
6

Open or update the PR

Checks whether a PR already exists for the current branch. If yes, it updates the title and body in place — never converting a ready-for-review PR back to draft. If no PR exists, it opens a new draft PR.
7

Write the PR body

The body leads with Why (the motivation, captured from your conversation with Codex) followed by What Changed (the net implementation diff). Images in existing PR bodies are always preserved.

​
PR title convention

Titles follow the conventional commit format: 
<type>(<scope>): <subject>
TypeWhen to use
featNew user-facing feature
fixBug fix for users
docsDocumentation changes
styleFormatting, missing semicolons — no logic change
refactorCode restructuring with no behavior change
testAdding or refactoring tests
choreBuild tooling, dependency updates, etc.
<scope> is optional and names the component, service, or subsystem being changed.

​
Default prompt

When you install the skill, its default prompt is:
“Prepare this branch for review: stage intended changes, write a focused commit, and open a PR.”

​
Installing

$skill-installer yeet
Restart Codex after installing to pick up the new skill.

Build docs developers (and LLMs) love

Get started for freeTalk to us