domains / families / devops / yeet

yeet

combined

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

When to use

When not to use

Skill page

Conflict

The two skills share the same core workflow (stage, commit, push, PR) but diverge significantly on naming conventions, PR template handling, and PR body composition. The openai/skills version is more comprehensive, including specific logic for discovering and applying GitHub PR templates, handling existing PRs (updating vs creating), and detailed guidelines for PR title formatting (conventional commits) and body content (preserving images, explaining 'why'). The Vibe-Skills version uses a different naming convention (prefixing with 'codex/') and lacks the template discovery and existing PR logic. Combining them is necessary to capture the robust template handling and PR management from the first, while acknowledging the specific naming preference of the second, though the first is generally superior in completeness. However, since the prompt asks to combine when copies overlap but each has material steps the others lack, and they disagree on naming, a combined instruction is appropriate to reflect the union of capabilities, specifically the template handling which is a major material step in the first copy.