yeet

Automate GitHub publishing from branch creation to draft pull request.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill yeet-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/github/skills/yeet
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill yeet-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) components.

What problem does it solve?

This skill solves the friction of manual Git and GitHub CLI operations by automating the branch creation, staging, committing, pushing, and draft pull request generation process in a single, verified workflow.

Core Features & Use Cases

  • Automated PR Lifecycle: Handles the entire sequence from local branch creation to opening a draft pull request on GitHub.
  • Safety Guardrails: Includes a branch guard to prevent accidental pushes to protected branches and ensures worktree changes are intentional.
  • Use Case: After implementing a feature, use this skill to automatically stage your changes, commit them with a conventional message, push to a new branch, and open a draft PR for review.

Quick Start

Use the yeet skill to publish my current changes to a new branch 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 automate creating a branch, committing, and opening a GitHub pull request?

Automating GitHub pull request creation requires a tool that sequences branch management, staging, committing, and draft PR generation into a single verified workflow. This ensures consistent commit messaging and safe remote synchronization without manual CLI operations.

What is the safest way to automate git workflow staging and pushing changes?

Safe git workflow automation includes branch guards that prevent accidental pushes to protected branches and validates the local repository state. This ensures worktree changes are intentional before staging, committing, and synchronizing with the remote repository.

Do I need Python and authenticated GitHub CLI access to automate pull request generation?

Yes, automating pull request generation requires Python for executing the automation scripts and authenticated GitHub CLI access to validate your local repository state and securely interact with your remote GitHub repository.

Can I prevent accidental pushes to protected branches during automated git workflows?

Preventing accidental pushes to protected branches during automated git workflows is handled by built-in safety guardrails. These guards verify your current branch and ensure worktree changes are intentional before executing any remote synchronization.

How do I generate a draft pull request with a conventional commit message from local changes?

Generating a draft pull request from local changes involves automatically staging your worktree, applying a conventional commit message, pushing to a new branch, and opening a draft PR on GitHub for review in a single end-to-end workflow.