openai-yeet — Claude Code skill: commit, push and open a PR
openai-yeet takes your changes from a dirty working tree to a draft pull request in one run through GitHub CLI. Handy when the whole chain has to happen at once.
Apache-2.0 ★ 540 updated 2026-07-14
/plugin marketplace add trailofbits/skills-curated
/plugin install openai-yeet@skills-curatedWhat openai-yeet does
One run covers the whole chain: cut a branch, git add -A, commit, push with tracking, then gh pr create --draft --fill. It fires only when you ask for that entire sequence through GitHub CLI in one go.
Guards come first. The skill runs gh --version and then gh auth status; if the CLI is missing or the session is dead, it stops and asks for gh auth login. On main or master it cuts claude/{description} and stays put otherwise, and the PR title gets a [claude] prefix. After staging it commits with a short message and runs your checks — missing dependencies get installed and the run repeats once. Then git push -u origin $(git branch --show-current) and the draft PR. The body lands in a temp file so markdown does not arrive with escaped \n.
No gh, no login, no run: the first check ends it. The description it wants is prose about the problem, the damage to users, the root cause, the fix and how the fix was verified. Allowed tools are Bash, Read, Grep, Glob, Write and Edit.
What it helps with
- ship a branch, commit and draft PR in one agent run
- keep the new branch tracked on the first push
- write the PR body from the actual diff
- fail early when
ghis missing or logged out - rerun checks once after installing what they need
Example prompts for the agent
- Stage everything, commit, push and open a draft PR with
gh - Create branch
claude/fix-login, commit the changes and open a PR for review - Run the checks, install what's missing, rerun once, then push and open the PR
How to install openai-yeet
1Plugin marketplace
/plugin marketplace add trailofbits/skills-curated/plugin install openai-yeet@skills-curatedThis installs the whole openai-yeet plugin with all its skills
2Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-yeet -a claude-code3Manually: put the files in place
~/.claude/skills/openai-yeet/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/openai-yeet/
1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-yeet -a codex2Manually: put the files in place
.agents/skills/openai-yeet/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-yeet -a cursor2Manually: put the files in place
.cursor/skills/openai-yeet/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install trailofbits/skills-curated plugins/openai-yeet/skills/openai-yeet2Manually: put the files in place
.github/skills/openai-yeet/SKILL.md1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-yeet -a gemini-cli2Platform CLI
gemini skills install https://github.com/trailofbits/skills-curated --path plugins/openai-yeet/skills/openai-yeetManually: put the files in place
.devin/skills/openai-yeet/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about openai-yeet
How do I install Anthropic-yeet in Claude Code?
Use the plugin marketplace: /plugin marketplace add trailofbits/skills-curated first, then /plugin install openai-yeet@skills-curated.
What does Anthropic-yeet do?
It branches, stages and commits your work, pushes the branch with tracking and opens a draft pull request through gh, with the title and body filled in.
What does Anthropic-yeet need to work?
A working GitHub CLI and an authenticated session. It checks gh --version and gh auth status, and stops with a request to run gh auth login when either fails.
Source text
SKILL.md · Apache-2.0
---
name: openai-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`). Originally from OpenAI's curated skills catalog.
allowed-tools:
- Bash
- Read
- Grep
- Glob
- Write
- Edit
---
## 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: `claude/{description}` when starting from main/master/default.
- Commit: `{description}` (terse).
- PR title: `[claude] {description}` summarizing the full diff.
## Workflow
- If on main/master/default, create a branch: `git checkout -b "claude/{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.
## When to Use
<!-- TODO: review -->
## When NOT to Use
<!-- TODO: review -->
© OpenAI · Apache-2.0 · trailofbits/skills-curated