About yeet
A skill for committing repository changes, pushing a branch, and opening a draft pull request with GitHub CLI. It is intended for developers and prescribes branch naming, checks, and a detailed PR description.
Key features
- 01GitHub CLI and authentication checks
- 02Branch naming and creation rules
- 03Stage and commit repository changes
- 04Push branch with upstream tracking
- 05Create draft pull requests
Use cases
- 01Submitting a code change for review
- 02Creating a draft PR from a working branch
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ davila7/ claude-code-templates --skill yeetAfter installing, type/yeetin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
LICENSE.txtagents/openai.yamlassets/yeet-small.svgDetails
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:
codex/{description}when starting from main/master/default. - Commit:
{description}(terse). - PR title:
[codex] {description}summarizing the full diff.
Workflow
- If on main/master/default, create a branch:
git checkout -b "codex/{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