yeet

Stage changes, commit, and open a GitHub pull request via gh.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/bl1nk-bot/skills-cli --skill yeet-bl1nk-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/bl1nk-bot/skills-cli/tree/main/skills/yeet
Command: npx skills add https://github.com/bl1nk-bot/skills-cli --skill yeet-bl1nk-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage changes, commit, and open a PR in a streamlined GitHub workflow using the GitHub CLI, reducing context-switching and manual steps.

Core Features & Use Cases

  • Branch-aware automation: Automatically names branches (codex/{description}) when starting from main/default, and stages changes for PR readiness.
  • One-flow PR creation: Stages, commits, and opens a PR via gh in a single, auditable step.
  • Prerequisites enforcement: Validates gh presence and authenticated session before proceeding to avoid partial runs.

Quick Start

Stage your changes, commit with a concise description, and open a pull request 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 staging, committing, and opening a pull request in one step?

To automate GitHub workflow actions, this Skill stages changes with git add -A, commits with a concise message, and uses gh pr create to open a PR in a single auditable step, reducing manual context-switching.

What's the best way to create a feature branch and PR from the default branch using the GitHub CLI?

Creating a PR from the default branch is handled by branch-aware automation that names branches using the codex/{description} convention, stages changes, commits, and opens the PR via gh without manual intervention.

Do I need the GitHub CLI installed and authenticated to automate PR creation?

Yes, GitHub CLI (gh) must be installed and authenticated. The Skill enforces prerequisites by validating gh presence and the authenticated session before proceeding to avoid partial runs or failed automation.

Can I use this automated commit and PR workflow when my main branch is protected?

Yes, this workflow is designed for individual developers and small teams where default branches are protected. It stages changes and opens PRs via gh, ensuring proper branch naming and status checks without direct commits to main.

How does the staging process work before committing changes for a pull request?

The staging process runs git status -sb to check the repository state, followed by git add -A to stage all changes. It then commits with a terse description before opening the PR using the GitHub CLI.