yeet

Stage, commit, push, and open a GitHub pull request using gh.

2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/alanharrryy-wq/hitech-os --skill yeet-alanharrryy-wq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/alanharrryy-wq/hitech-os/tree/main/.agents/skills/Z_integrator/yeet
Command: npx skills add https://github.com/alanharrryy-wq/hitech-os --skill yeet-alanharrryy-wq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, multi-step process of staging changes, composing a focused commit message, pushing to a branch, and opening a pull request, by providing an integrated GitHub CLI workflow.

Core Features & Use Cases

  • Unified GitHub workflow: stage changes, commit with a concise message, push to the feature branch, and open a PR in one seamless sequence.
  • Enforces branch naming conventions and checks for authenticated gh sessions to prevent failed PRs.
  • Use case: a developer wants to submit a small feature with a single command flow to expedite code review and merge.

Quick Start

Execute the complete GitHub flow by staging changes, committing with a concise message, pushing, and opening a PR using gh.

Frequently Asked Questions about yeet

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

FAQPage Schema
How do I stage, commit, push, and open a pull request in one command?

To stage, commit, push, and open a pull request in one flow, you need an integrated GitHub CLI workflow. This skill automates the entire sequence, enforcing consistent commit message styles and branch naming conventions to expedite code review.

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

Yes, you need the GitHub CLI (gh) installed and authenticated to automate opening a pull request. The workflow checks for an authenticated gh session to prevent failed PRs and ensures branch naming conventions are applied.

What is the best way to streamline code changes for GitHub code review?

The best way to streamline code changes for GitHub is using an integrated CLI workflow that unifies staging, committing, pushing, and PR creation. This eliminates manual multi-step processes and enforces consistent commit messages across branches.

How does a unified GitHub workflow handle branch naming and commit messages?

A unified GitHub workflow handles branch naming and commit messages by applying scripted conventions automatically. It stages changes, composes a concise commit message, pushes to the feature branch, and opens a PR seamlessly.

Can I use this automated git workflow for small feature submissions?

Yes, you can use this automated git workflow for small feature submissions. It is designed for developers who want to submit features with a single command flow, expediting the code review and merge process.

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

An automated pull request workflow fails to open a PR if the GitHub CLI is not installed or authenticated. This skill satisfies gh authentication prerequisites and enforces branch naming conventions to prevent failed PR creation.