Agent skill · software engineering · openai
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`).
Why this skill is useful
Adds a comprehensive script for automating GitHub pull requests with specific workflows and templates that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. Requires github account access. About 4k tokens when loaded. Last updated 2026-07-14. 24,594 stars on the source repository.
What this skill does
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. PR template discovery Before creating the PR, resolve the repository root and look for the active GitHub PR template from there: Template candidates, in order: .github/pullrequesttemplate.md .github/PULLREQUESTTEMPLATE.md One .md file under .github/pullrequesttemplate/ One .md file under .github/PULLREQUESTTEMPLATE/ Use paths as emitted from the repository root, such as .github/pullrequesttemplate.md, not ./.github/pullrequesttemplate.md. If exactly one template is found, read it before composing the final PR body and pass it to gh pr create with --template "$template". If multiple template files are found, stop before PR creation and ask which template to use. If no template exists, use the fallback body shape in this skill. 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. Discover and read the repository PR template, if any. Check whether the current branch already has a PR: gh pr view "$(git branch --show-current)" --json number,isDraft,url If a PR already exists, update that PR in place. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills openai/yeet