yeet

Automate GitHub pull request creation using the GitHub CLI.

Updated Apr 26, 2026

Search Tags:#code review #pull request #workflow automation #CLI #GitHub

Ready to run

npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill yeet-renzo-tognella

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/Renzo-Tognella/UniversalThingsForMyAgents/tree/main/skills/yeet
Command: npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill yeet-renzo-tognella

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of staging, committing, pushing, and opening a GitHub pull request in one command, using the GitHub CLI (gh).

Core Features & Use Cases

Single Command Workflow: Automates the complete GitHub pull request workflow with one command.
GitHub CLI Integration: Requires the GitHub CLI (gh) to be installed and authenticated.
Branch and Commit Naming: Automates the creation of branches and commits with the correct naming conventions.
PR Creation: Opens a pull request with a summary of the changes.
Use Case: Ideal for developers who want to quickly create a pull request without manually executing multiple commands.

Quick Start

Run the command 'yeet' to initiate the GitHub pull request workflow.

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 GitHub pull request from the command line?▼

To automate creating a GitHub pull request from the command line, you can use a workflow automation command that handles branch creation, staging, committing, pushing, and opening the PR in one step via the GitHub CLI.

Do I need to install the GitHub CLI to automate my pull request workflow?▼

Yes, you need to install and authenticate the GitHub CLI (`gh`) to automate your pull request workflow, as the automation script relies on it to push changes and open pull requests on your remote repository.

What's the best way to streamline staging and pushing code for a GitHub PR?▼

The best way to streamline staging and pushing code for a GitHub PR is using a single command workflow that automatically stages your changes, creates a correctly named branch, commits, pushes to the remote, and opens the pull request.

Can I automatically generate branch names and commit messages when opening a pull request?▼

Yes, you can automatically generate branch names and commit messages when opening a pull request by using CLI workflow automation that handles the naming conventions for you during the staging and committing process.

Why does my automated pull request workflow fail to open a PR on GitHub?▼

Your automated pull request workflow may fail to open a PR on GitHub if your GitHub CLI session is not authenticated, or if the `gh` dependency is missing from your local environment.

Does the yeet command support opening pull requests with an automated summary of changes?▼

Yes, the yeet command supports opening pull requests by automatically generating a summary of your staged changes to populate the PR description when it executes the GitHub CLI workflow.