yeet

Validate scope, stage, commit, push, and open a draft PR.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill yeet-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yeet
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.codex/plugins/cache/openai-curated/github/314574a046f21938025ae443f9c6dbbd0c2c9b7a/skills/yeet
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill yeet-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish local changes to GitHub by guiding the full local-to-PR workflow, reducing context switching and mistakes in branching, staging, committing, and PR creation.

Core Features & Use Cases

  • Guided git flow: Validate scope, create or reuse a branch, stage changes, and commit with a concise message.
  • PR orchestration: Push to remote and open a draft PR via the GitHub app, with gh as fallback when app/connector is unavailable.
  • Safety checks: Enforce authentication, require a clean working tree, and prevent accidental pushes of unrelated changes.

Quick Start

Confirm the scope of changes, then push the branch and open a draft pull request.

Frequently Asked Questions about yeet

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

FAQPage Schema
How do I automate creating a draft pull request from local changes?

Automate creating a draft PR by validating scope, staging, committing, and pushing local changes to a remote GitHub branch. This guided flow orchestrates the full publish process and opens a draft pull request safely.

What is the best way to publish local git changes to GitHub without mistakes?

Publish local git changes safely by enforcing a clean working tree and validating change scope before staging. This prevents accidental pushes of unrelated changes and orchestrates branch creation, committing, and draft PR opening.

Do I need gh CLI installed to open a draft PR from a local branch?

You need gh CLI configured as a fallback to open a draft PR when the GitHub app or connector is unavailable. The workflow requires Git and gh CLI setup, along with repository access, to complete the pull request process.

Can I use this guided git flow for feature work in local repos?

Use this guided git flow for individual developers and small teams performing feature work in local repos. It validates scope, creates or reuses branches, and orchestrates the end-to-end publish flow to open a draft pull request.

Why does the local-to-PR workflow require a clean working tree?

The local-to-PR workflow requires a clean working tree to enforce safety checks and prevent accidental pushes of unrelated changes. Validating scope before staging ensures only intended modifications are committed and published to GitHub.