Back to catalog / Developer tools
Yeet: run the GitHub release workflow only on explicit request
Check auth, branch, and PR template, validate, then create a draft PR reflecting actual changes.
Skills
Trigger only when the user explicitly requests the full stage/commit/push/PR sequence. Check `gh --version`, `gh auth status`, branch, and diff without reading/printing tokens. If on the default branch, follow the source branch rule. Read the PR template; use one template, ask when multiple exist. Review scope, exclude credentials, and run appropriate checks before staging/committing/pushing and creating a draft PR. Update an existing PR in place while preserving draft/ready state. On auth errors, follow gh auth guidance rather than blindly retrying.
Permissions
Prerequisites
- Use only when explicitly asked to stage, commit, push, and open/update a GitHub PR in one flow.
Permissions
- Stages, commits, pushes, and creates/updates a PR; these are distinct external side effects.
Limitations
Requires authenticated gh; multiple templates require user choice and PR state must be preserved.
Pinned upstream source
- Repository
- openai/skills
- File path
- skills/.curated/yeet/SKILL.md
- Pinned commit
49f948faa9258a0c61caceaf225e179651397431- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
`gh` CLI · repository PR template · Git status/checks
Main topic
Take a coding Agent change from context to verification