yeet

SkillDev tools

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

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the yeet skill

What this skill tells your AI

The instructions your AI receives, as published by vana-com/personal-server in .agents/skills/yeet/SKILL.md and read by ahel’s review.

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.

Branch: (feat|fix|...)/{description} when starting from main/master/default. Follow conventional commits (https://www.conventionalcommits.org/en/v1.0.0/)
Commit: {description} (terse).
PR title: (feat|fix|...): {description} summarizing the full diff.

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

Advanced