skills.rest
dougdliu
dougdliuCOMMUNITY
Explore all skills by this author →
GitHub

yeet

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

Updated May 8, 2026
Search Tags:#automation#git#workflow#github#gh#branch-management#pull-request
One-click install
npx skills add https://github.com/dougdliu/FRC_AI_Mega_Project --skill yeet-dougdliu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/dougdliu/FRC_AI_Mega_Project/tree/main/skills/codex/yeet
Command: npx skills add https://github.com/dougdliu/FRC_AI_Mega_Project --skill yeet-dougdliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Staging, committing, pushing, and opening a pull request across feature branches typically requires several manual steps and toggling between tools. This skill consolidates the flow into a single, repeatable pattern powered by the GitHub CLI, reducing context-switching and errors.

Core Features & Use Cases

  • Single-flow PR creation: Stage changes, commit with a concise message, push to origin, and open a pull request using gh.
  • Guidance and guardrails: Enforces authentication prerequisites and branch naming conventions to keep workflows consistent.
  • Use cases: Ideal for frequent feature work, quick PR turnarounds, and teams that want predictable PR descriptions and statuses.

Quick Start

Instruct the AI to create a new branch, commit with a concise message, push to origin, and open a PR using the GitHub CLI.

Frequently Asked Questions about yeet

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

FAQPage Schema
How do I automate git PR creation from staging to opening a pull request on GitHub?▼

Automating git PR creation involves staging changes, committing with a concise message, pushing to origin, and opening a pull request using gh. This single-flow pipeline reduces manual steps and context-switching across feature branches.

What's the best way to streamline a GitHub workflow for frequent feature branches?▼

Streamlining a GitHub workflow uses a single repeatable pattern powered by the GitHub CLI to stage, commit, push, and open pull requests. This approach enforces branch naming conventions and predictable PR descriptions for quick turnarounds.

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

Yes, automating pull request creation requires the GitHub CLI to be available and authenticated. The workflow enforces these prerequisites to ensure successful pushes to origin and PR generation across feature branches.

Can I enforce branch naming conventions when automating git commits and pushes?▼

Yes, you can enforce branch naming conventions during automated git commits and pushes. The workflow applies guardrails that check branch names and authentication prerequisites to keep feature branch statuses consistent.

Why does my automated git workflow result in inconsistent PR descriptions?▼

Inconsistent PR descriptions occur when manual steps lack enforced guardrails. Automating the pipeline with gh enforces clear PR descriptions and branch naming conventions, ensuring predictable code review statuses across feature branches.

Related Skills

Explore More Software Engineering Skills→
Sacred-GSacred-G
2

yeet

Stage, commit, push, and open a GitHub pull request via GitHub CLI.

Community
Intermediate
omerakbenomerakben
1

git-workflow-deployment

Automate Git branching, CI/CD gates, and Vercel production deployments.

Community
Intermediate
Leep-GHLeep-GH

pr-lifecycle

Automate GitHub issue-to-PR-to-merge workflows with readiness checks.

Community
Advanced
philoserfphiloserf
13

git-workflow

Automate Git workflows with atomic commits, branch management, and PR creation.

Community
Advanced