Codex Skill

Yeet

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`).

Editor's Note

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`). Covers prerequisites, naming conventions, workflow.

Install

npx skills add https://github.com/openai/skills --skill yeet

Page Outline

PrerequisitesNaming conventionsWorkflow

Source Content

Normalized top-level metadata comes from the directory layer. The body below is the upstream source content for this item.

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: `{description}` when starting from main/master/default.
Commit: `{description}` (terse).
PR title: `{description}` summarizing the full diff.

Workflow

If on main/master/default, create a branch: `git checkout -b "{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.

Related Items

Codex Skill

Gh Pr Checks Plan Fix

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

Codex Skill

PR Comment Handler

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

Codex Skill

Playwright CLI Skill

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.