yeet

Automate GitHub publishing from branch creation to draft pull requests.

4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mymx2/foreman --skill yeet-mymx2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/mymx2/foreman/tree/main/.agents/skills/yeet
Command: npx skills add https://github.com/mymx2/foreman --skill yeet-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes assets (resource) components.

What problem does it solve?

This skill eliminates the friction of manual Git operations and repetitive PR creation by automating the entire publish flow from local changes to a draft pull request.

Core Features & Use Cases

  • Automated PR Lifecycle: Handles branch creation, staging, committing, pushing, and draft PR generation in one cohesive flow.
  • Safety-First Staging: Prevents accidental commits by requiring explicit scope confirmation when the working tree contains mixed changes.
  • Use Case: When you finish a feature, use this skill to automatically create a branch, commit your work with a clear description, push to origin, and open a draft PR for review without leaving your terminal.

Quick Start

Use the yeet skill to stage my current changes, commit them with a descriptive message, push the 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 my git workflow and open a draft pull request from the terminal?

To automate your git workflow, this skill handles branch creation, staging, committing, pushing, and draft pull request generation in a single flow using the GitHub CLI. It requires a configured local git repository to execute operations securely.

What is the safest way to stage mixed changes before creating a GitHub pull request?

The safest way to stage mixed changes is using a safety-first approach that requires explicit scope confirmation. This prevents accidental commits by ensuring you review and confirm exactly which modifications are included before pushing to origin.

Do I need the GitHub CLI installed to automate pull request creation?

Yes, you need the GitHub CLI (gh) installed to automate pull request creation. This skill depends on gh to securely execute remote operations, push branches to origin, and generate draft pull requests on your repository.

Can I use this automated git workflow for consistent commit hygiene across software development cycles?

Yes, you can use this automated git workflow for consistent commit hygiene across development cycles. It applies to software development requiring rapid PR generation by standardizing branch management, staging, and commit descriptions.

Why does automated branch management require explicit confirmation for mixed changes?

Automated branch management requires explicit confirmation for mixed changes to prevent accidental commits. When your working tree contains unrelated modifications, the skill prompts for scope confirmation to ensure only intended files are committed and pushed.