yeet

Stage, commit, push, and open a GitHub PR via gh.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/metric-space-ai/ctox --skill yeet-metric-space-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/metric-space-ai/ctox/tree/main/skills/packs/git/yeet
Command: npx skills add https://github.com/metric-space-ai/ctox --skill yeet-metric-space-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically streamline the Git workflow to stage changes, commit with a clear message, push to a feature branch, and open a PR using gh, reducing manual steps and context switching.

Core Features & Use Cases

  • Stage changes, review status, and maintain a clean feature-branch workflow.
  • Commit with a concise, descriptive message to support clear code reviews.
  • Open a PR with a standardized title/body using gh, enabling automated checks and faster collaboration.

Use Case: When finishing a small feature, stage the changes, commit a concise description, push the branch, and open a PR in one seamless flow.

Quick Start

Stage changes, commit with a concise description, push, and open a PR using gh in a single workflow.

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 Git workflow?

You can automate this Git workflow by staging changes, committing with a descriptive message, pushing to a feature branch, and opening a pull request using the GitHub CLI (gh) in a single seamless flow.

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

Yes, automating the pull request creation step requires the GitHub CLI (gh) to be installed and authenticated, as the workflow relies on it to open the PR with a standardized title and body.

What is the best way to streamline feature-branch development and PR-driven code reviews?

Streamlining feature-branch development involves automating the sequence of staging changes, committing concise descriptions, pushing the branch, and opening a PR via gh to trigger automated checks and enable faster collaboration.

Can I use this automated git workflow for collaborative coding tasks in any configured repository?

Yes, this workflow applies to collaborative coding tasks and feature-branch development within software projects, provided you have a configured repository, gh authentication, and follow the specified branch naming conventions.

Why does opening a pull request manually cause context switching during software development?

Manually executing separate git commands for staging, committing, pushing, and opening a pull request forces context switching, which an automated gh workflow eliminates by combining these steps into one continuous flow.