yeet

Commits local changes, pushes the branch, and opens a draft GitHub pull request.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill yeet-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/AarnavBaddam/skills/tree/main/yeet
Command: npx skills add https://github.com/AarnavBaddam/skills --skill yeet-aarnavbaddam

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 what to stage, creating a branch, writing a commit, pushing, and opening a pull request. This Skill automates that entire flow while protecting you from accidentally committing unrelated changes. ## Core Features & Use Cases - Scoped Staging: Inspects the working tree and asks which files belong in the PR instead of blindly running git add -A. - Branch and Commit Automation: Creates an agent/{description} branch from the default branch, commits tersely, and pushes with tracking. - Draft PR Creation: Opens a draft pull request via the GitHub connector, falling back to the gh CLI when the connector cannot infer the repository or branch. - Use Case: You finished a bug fix on a mixed working tree. The Skill confirms which files belong to the fix, commits only those, pushes a new 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 changes and open a GitHub pull request in one flow?

This Skill runs the full publish flow: it inspects git status, confirms which files belong in scope, creates a branch if needed, commits, pushes with tracking, and opens a draft PR through the GitHub connector or gh CLI.

How do I avoid committing unrelated changes with git add -A?

The Skill inspects the working tree first and asks which files belong in the PR when changes are mixed. It stages explicit file paths and only uses git add -A after you confirm the whole worktree is in scope.

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 does it use gh pr create instead of the GitHub connector?

It falls back to gh pr create --draft when the connector cannot infer the repository or head branch, or when pushing from a fork where cross-repository head semantics are not handled cleanly by the connector.

Can I open a ready-for-review PR instead of a draft?

The Skill defaults to draft pull requests as a safety measure. It only opens a ready-for-review PR when you explicitly ask for one.