About yeet
yeet is a skill that guides GitHub changes from branch preparation through commit, checks, push, and draft pull request creation. It requires an authenticated GitHub CLI session and specifies conventions for commits and detailed PR descriptions.
Key features
- 01Check GitHub CLI installation and authentication
- 02Create a branch when starting from the default branch
- 03Stage and commit changes
- 04Run checks and push with tracking
- 05Create and describe a draft pull request
Use cases
- 01Prepare a code change for review
- 02Push a feature branch to GitHub
- 03Open a draft PR with validation details
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ mxyhi/ ok-skills --skill yeetAfter installing, type/yeetin Claude Code to confirm it loaded.
Bundled filesLICENSE.txtagents/openai.yaml
Details
From the project READMEPrerequisites
- Require GitHub CLI
gh. Checkgh --version. If missing, ask the user to installghand stop. - Require authenticated
ghsession. Rungh auth status. If not authenticated, ask the user to rungh auth login(and re-rungh 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 -sbthengit 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.
Comments
Markdown supported