Yeet — Agent Skill by JetBrains

From the author

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

— the description by OpenAI

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The yeet skill provides a streamlined, automated procedure for developers to stage changes, commit them, push to a remote repository, and open a GitHub pull request using the GitHub CLI. It enforces specific naming conventions for branches and pull requests while ensuring the environment is properly authenticated before execution.

What it does

Creates a new branch if the user is currently on the main or master branch.
Stages all local changes and commits them with a provided description.
Pushes the current branch to the remote origin with tracking enabled.
Opens a draft pull request on GitHub using the GitHub CLI.
Generates a detailed pull request description covering the issue, root cause, and fix.
Handles common Git push errors by pulling from the master branch before retrying.

When to use it

When you want to quickly push your current work and open a pull request in a single command.
When you need to follow standardized naming conventions for branches and PR titles.
When you are working in a terminal environment and have the GitHub CLI installed.

Advantages

Reduces manual overhead by combining multiple Git and GitHub CLI commands into one flow.
Ensures consistent naming conventions for branches and pull requests.
Automates the creation of detailed pull request descriptions.
Includes built-in checks for authentication and tool availability.

Usage examples

“yeet add user authentication logic”: The agent stages all changes, commits them with the message 'add user authentication logic', pushes the branch, and opens a draft PR with a detailed description.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/jetbrains/yeet/download
Unzip it into the cross-client skills folder of your project:
```
mkdir -p .agents/skills && unzip yeet.zip -d .agents/skills
```

Documentation by OpenAI

Prerequisites

Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.

Naming conventions

Branch: codex/{description} when starting from main/master/default.
Commit: {description} (terse).
PR title: [codex] {description} summarizing the full diff.

Workflow

If on main/master/default, create a branch: git checkout -b "codex/{description}"
Otherwise stay on the current branch.
Confirm status, then stage everything: git status -sb then git add -A.
Commit tersely with the description: git commit -m "{description}"
Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
Push with tracking: git push -u origin $(git branch --show-current)
If git push fails due to workflow auth errors, pull from master and retry the push.
Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

Files

ATTRIBUTION.mdAdded by AutoGineer865 B
LICENSE.txt10.5 KiB
SKILL.md1.8 KiB
agents/openai.yaml273 B
assets/yeet-small.svg967 B
assets/yeet.png1.2 KiB

SKILL.md

Prerequisites

Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.

Naming conventions

Branch: codex/{description} when starting from main/master/default.
Commit: {description} (terse).
PR title: [codex] {description} summarizing the full diff.

Workflow

If on main/master/default, create a branch: git checkout -b "codex/{description}"
Otherwise stay on the current branch.
Confirm status, then stage everything: git status -sb then git add -A.
Commit tersely with the description: git commit -m "{description}"
Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
Push with tracking: git push -u origin $(git branch --show-current)
If git push fails due to workflow auth errors, pull from master and retry the push.
Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Git Guardrails Claude Code
Matt Pocock· Community
Implement safety guardrails for Claude Code to prevent accidental execution of destructive Git commands.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository317.5k
Setup Pre Commit
Matt Pocock· Community
Automates the configuration of Husky pre-commit hooks, lint-staged, and Prettier for your project.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
CI CD And Automation
Addy Osmani· Community
A comprehensive framework for establishing automated CI/CD pipelines, quality gates, and deployment strategies.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Git Workflow And Versioning
Addy Osmani· Community
A comprehensive framework for disciplined Git workflows, atomic commits, and semantic versioning to ensure manageable and reliable code history.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Git Advanced Workflows
Seth Hobson· Community
Master advanced Git techniques for history management, bug isolation, and recovery.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Github Actions Templates
Seth Hobson· Community
A collection of production-ready GitHub Actions workflow templates for CI/CD automation.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository42.3k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download yeet.zip

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by OpenAI

Prerequisites

Naming conventions

Workflow

Files

SKILL.md

Prerequisites

Naming conventions

Workflow

Requirements and compatibility

Security

Attribution and licence

Related skills

Git Guardrails Claude Code

Setup Pre Commit

CI CD And Automation

Git Workflow And Versioning

Git Advanced Workflows

Github Actions Templates

Download ZIP