skills.rest
shalevamin
shalevaminCOMMUNITY
Explore all skills by this author →
GitHub

yeet

Stage, commit, and push code changes to a new branch and open a draft GitHub pull request.

Updated Mar 7, 2026
Search Tags:#automation#git#code review#pull request#developer workflow#github
One-click install
npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill yeet-shalevamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/yeet
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill yeet-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the entire process of preparing code changes for review, from staging to opening a pull request, streamlining the development workflow.

Core Features & Use Cases

  • Automated Git Operations: Stages all changes, creates a concise commit message, and pushes to a new branch.
  • GitHub CLI Integration: Opens a draft pull request with a pre-filled title and body using the gh CLI.
  • Use Case: After completing a feature or bug fix, you can use this Skill to quickly get your changes ready for a code review without manually running multiple Git and GitHub commands.

Quick Start

Use the yeet skill to prepare this branch for review by staging changes, writing a commit, and opening a PR.

Frequently Asked Questions about yeet

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

FAQPage Schema
How do I automate staging, committing, and opening a GitHub pull request?▼

Automating staging, committing, and opening a GitHub pull request is done by pushing changes to a new branch and using the GitHub CLI to open a draft PR. This streamlines the developer workflow by enforcing branch and commit naming conventions automatically.

What is the best way to streamline my developer workflow for code reviews?▼

Streamlining your developer workflow for code reviews is achieved by automating Git operations and opening draft pull requests directly from the command line. This removes the need to manually run multiple Git and GitHub commands after completing a feature.

Do I need the GitHub CLI installed to open a draft pull request from the command line?▼

Yes, you need the GitHub CLI installed and authenticated to open a draft pull request from the command line. The automation relies entirely on the GitHub CLI to create the PR with a pre-filled title and body after pushing the code.

Can I enforce naming conventions for Git branches and commit messages during automation?▼

Yes, you can enforce naming conventions for Git branches and commit messages during automation. The process specifically enforces these conventions while staging changes, creating a concise commit message, and pushing to a new branch.

How does automated Git operations handle code changes before opening a PR?▼

Automated Git operations handle code changes by staging all local modifications, creating a concise commit message, and pushing everything to a new branch. Afterward, a draft pull request is opened to prepare the changes for review.

Related Skills

Explore More Software Engineering Skills→
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
thanhquan3010thanhquan3010

yeet

Stage, commit, and push code changes, then open a draft GitHub pull request via the GitHub CLI.

Community
Intermediate
ianclearyiancleary
1

git-push-pr

Automate Git staging, committing, pushing, and pull request management with GitHub CLI.

Community
Intermediate