yeet

Commit, push, and open draft pull requests on GitHub from local changes.

68|25|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/rojim666/SztuCode --skill yeet-rojim666
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/rojim666/SztuCode/tree/main/py-runtime/src/sztu_code/core/skills/builtin/yeet
Command: npx skills add https://github.com/rojim666/SztuCode --skill yeet-rojim666

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Publishing local work to GitHub involves many error-prone steps: deciding which changes belong in the PR, creating a branch, staging, committing, pushing, and opening a pull request. This Skill automates that entire flow while protecting you from accidentally staging unrelated changes or pushing without confirmation. ## Core Features & Use Cases - Scoped Staging and Committing: Inspects the working tree, asks which files belong in the PR when changes are mixed, and commits with a terse, meaningful message. - Branch and Push Automation: Creates a codex/{description} branch when starting from a default branch and pushes with upstream tracking. - Draft PR Creation: Opens a draft pull request via the GitHub app connector, falling back to gh pr create when the connector cannot infer the repository or branch. - Use Case: You finished a bug fix alongside some unrelated experiments in your working tree. The Skill confirms which files belong in the PR, commits only those, pushes the branch, and opens a draft PR with a structured description. ## Quick Start Use $yeet to confirm the intended changes, create a focused commit, push it, and open a draft pull request.

Frequently Asked Questions about yeet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit and push local changes and open a GitHub pull request?▼

Run the publish flow which inspects git status, confirms which files belong in the PR, commits them with a terse message, pushes the branch with tracking, and opens a draft pull request via the GitHub app or gh CLI fallback.

How do I avoid staging unrelated changes when creating a PR?▼

The workflow runs git status -sb and inspects the diff before staging. If the worktree contains unrelated changes, it asks which files belong in the PR and stages only explicit file paths instead of using git add -A.

Does this workflow require the GitHub CLI gh?▼

Yes, gh must be installed and authenticated. The skill checks gh --version and gh auth status first, and asks you to run gh auth login if the session is not authenticated before continuing.

When is gh pr create used instead of the GitHub app connector?▼

The gh fallback is used when pushing from a fork, when the PR target differs from the pushed remote, or when the connector cannot infer the repository or head branch cleanly. Cross-repository PRs are created with gh pr create --draft.

Why does the workflow open a draft PR instead of a ready PR?▼

Draft PRs are the default to prevent premature review requests. A ready-for-review PR is only created when the user explicitly asks for it, keeping the publish flow safe by default.