yeet

Publish local code changes to GitHub as a draft PR.

Updated Apr 14, 2026

Search Tags:#automation #git #workflow #commit #github #publish #pr

Ready to run

npx skills add https://github.com/dallay/opencode-docker --skill yeet-dallay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/yeet
Command: npx skills add https://github.com/dallay/opencode-docker --skill yeet-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish local changes to GitHub by guiding branch setup, commit, push, and draft PR creation.

Core Features & Use Cases

End-to-end publish workflow: create or adapt a local branch, stage and commit changes, push to origin, and open a draft PR using the configured integration.
Guardrails and checks: verify that a clean working tree exists, enforce conventional commits, and provide fallback path if integration cannot infer repo details.
Use Case: You finished a feature on a local branch and want to publish it to GitHub as a draft PR for review.

Quick Start

Run the Yeet workflow on your current feature branch to publish changes as a draft PR.

Frequently Asked Questions about yeet

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

FAQPage Schema

How do I publish local changes to GitHub as a draft PR?▼

To publish local changes to GitHub, this workflow guides branch setup, commits with a conventional message, pushes to origin, and opens a draft PR. It verifies a clean working tree and authenticated access before completing the publish process.

What do I need to create a draft PR from my local branch?▼

Creating a draft PR requires a clean working tree, a local repository with configured GitHub integration, and authenticated access. A descriptive conventional-commit style message is also needed to properly publish your code changes.

How to commit and push local code changes using conventional commits?▼

Committing and pushing local changes requires a clean working tree and a descriptive conventional-commit style message. The workflow stages your changes, commits them, pushes to origin, and opens a draft PR for review.

Can I create a GitHub PR from the CLI if my integration cannot infer repo details?▼

Yes, if the configured GitHub integration cannot infer repository details, the workflow provides a fallback path for CLI-based PR creation. This ensures you can still publish local changes and open a draft PR safely.

Does the publish workflow enforce a clean working tree before pushing to GitHub?▼

Yes, the publish workflow verifies that a clean working tree exists before guiding branch setup, commit, push, and draft PR creation. This guardrail ensures local changes are properly staged and committed before pushing to GitHub.

What is the best way to automate publishing a feature branch to GitHub?▼

Automating feature branch publishing involves guiding branch setup, enforcing conventional commits, pushing to origin, and opening a draft PR. This workflow applies guardrails like clean working tree verification and CLI fallback to publish safely.