AI SummaryAutomates the complete GitHub workflow (stage, commit, push, PR) via GitHub CLI in a single flow with consistent naming conventions. Developers who frequently create pull requests benefit from reduced repetitive command execution.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "yeet" skill in my project. Please run this command in my terminal: # Install skill into your project (5 files) mkdir -p .claude/skills/yeet && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/yeet/SKILL.md "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/yeet/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/yeet/LICENSE.txt "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/yeet/LICENSE.txt" && mkdir -p .claude/skills/yeet/agents && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/yeet/agents/openai.yaml "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/yeet/agents/openai.yaml" && mkdir -p .claude/skills/yeet/assets && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/yeet/assets/yeet-small.svg "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/yeet/assets/yeet-small.svg" && mkdir -p .claude/skills/yeet/assets && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/yeet/assets/yeet.png "https://raw.githubusercontent.com/openai/skills/main/skills/.curated/yeet/assets/yeet.png" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
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: {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.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster