AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The yeet skill streamlines the process of staging changes, committing them, pushing to a remote branch, and opening or updating a GitHub pull request. It integrates directly with the GitHub CLI (gh) to handle branch creation, template discovery, and PR metadata management. The skill ensures that PR titles follow conventional commit standards and that PR bodies are professionally formatted, incorporating repository-specific templates where available while preserving existing PR information.
What it does
- Stages all local changes and commits them using a provided description.
- Creates a new branch if the user is currently on the main or default branch.
- Pushes changes to the remote repository with tracking enabled.
- Detects and applies repository-specific GitHub pull request templates.
- Opens a new draft pull request or updates an existing one without altering its review status.
- Formats PR titles and bodies according to conventional commit standards and professional documentation practices.
When to use it
- When you have completed a set of changes and want to submit them for review in a single, automated step.
- When you need to quickly push a feature or fix and open a PR without manually running multiple git and gh commands.
- When you want to ensure your PR follows specific repository templates and naming conventions automatically.
Advantages
- Reduces manual overhead by chaining git and GitHub CLI operations.
- Ensures consistency in PR titles and descriptions across the repository.
- Respects existing PR templates and preserves critical information in existing pull requests.
- Prevents accidental creation of duplicate PRs by checking for existing ones on the current branch.
Usage examples
- “yeet feat: add user authentication”
- The agent stages all changes, commits them with the message 'feat: add user authentication', pushes the branch, and opens a draft PR using the repository's template.
- “yeet fix: resolve memory leak in parser”
- The agent commits the changes, pushes the branch, and updates the existing PR for the current branch with a new title and body reflecting the fix.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/openai/yeet/downloadUnzip 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. Checkgh --version. If missing, ask the user to installghand stop.Require authenticated
ghsession. Rungh auth status. If not authenticated, ask the user to rungh auth login(and re-rungh auth status) before continuing.
Naming conventions
Branch:
{description}when starting from main/master/default.Commit:
{description}(terse).PR title:
{description}summarizing the full diff.
PR template discovery
Before creating the PR, resolve the repository root and look for the active GitHub PR template from there:
repo_root="$(git rev-parse --show-toplevel)"Template candidates, in order:
.github/pull_request_template.md.github/PULL_REQUEST_TEMPLATE.mdOne
*.mdfile under.github/pull_request_template/One
*.mdfile under.github/PULL_REQUEST_TEMPLATE/
Use paths as emitted from the repository root, such as .github/pull_request_template.md, not ./.github/pull_request_template.md.
If exactly one template is found, read it before composing the final PR body and pass it to gh pr create with --template "$template".
If multiple template files are found, stop before PR creation and ask which template to use. If no template exists, use the fallback body shape in this skill.
Workflow
If on main/master/default, create a branch:
git checkout -b "{description}"Otherwise stay on the current branch.
Confirm status, then stage everything:
git status -sbthengit 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.
Discover and read the repository PR template, if any.
Check whether the current branch already has a PR:
gh pr view "$(git branch --show-current)" --json number,isDraft,urlIf a PR already exists, update that PR in place. Do not create another PR, and do not change whether the existing PR is draft or ready for review.
If no PR exists, open a new draft PR:
With one template:
GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --template "$template" --head "$(git branch --show-current)"Without a template:
GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head "$(git branch --show-current)"
Edit the PR title and body so they reflect the actual net change in the diff.
Write the PR description to a temp file with real newlines and pass it via
--body-fileorgh pr edit --body-fileto avoid\n-escaped markdown.
Determining the PR
When updating a PR created earlier in the flow, infer the PR from the current branch when possible:
git branch --show-current
gh pr view "$(git branch --show-current)" --json number --jq '.number'If this finds an existing PR, preserve its current review state. Never convert an existing ready-for-review PR back to draft as part of yeet; only new PRs created by this flow should start as draft.
PR Title
Format: <type>(<scope>): <subject>
<scope> is optional. A scope consist of a noun describing a section of the codebase (component, service or subsytem).
Example
feat: add hat wobble
^--^ ^------------^
| |
| +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.More Examples:
feat: (new feature for the user, not a new feature for build script)fix: (bug fix for the user, not a fix to a build script)docs: (changes to the documentation)style: (formatting, missing semi colons, etc; no production code change)refactor: (refactoring production code, eg. renaming a variable)test: (adding missing tests, refactoring tests; no production code change)chore: (updating grunt tasks etc; no production code change)
PR Body Contents
When invoked, use gh to edit the pull request body and title to reflect the contents of the specified PR. Make sure to check the existing pull request body to see if there is key information that should be preserved. For example, NEVER remove an image in the existing pull request body, as the author may have no way to recover it if you remove it.
When a repository PR template exists, adapt the final PR body to that template. Preserve meaningful headings, required checklists, and repo-specific prompts, but replace placeholder text with net-diff-specific content or N/A where the template asks for it. Do not discard template sections just because the fallback shape below is shorter.
It is critically important to explain why the change is being made. If the current conversation in which this skill is invoked has discussed the motivation, be sure to capture this in the pull request body.
The body should also explain what changed, but this should appear after the why.
Limit discussion to the net change of the commit. It is generally frowned upon to discuss changes that were attempted but later undone in the course of the development of the pull request. When rewriting the pull request body, you may need to eliminate details such as these when they are no longer appropriate / of interest to future readers.
Avoid references to absolute paths on my local disk. When talking about a path that is within the repository, simply use the repo-relative path.
Default to omitting Verification. Add it only when you have behavioral evidence worth preserving for reviewers: a reproduced bug, a before/after check, a targeted test that exercises the changed behavior, or a manual scenario with input and observed outcome. Do not use it for generic commands or automation results such as package tests, type checks, linters, formatters, pre-commit/pre-push hooks, or CI status.
If the repository template requires a validation or verification section, keep that section and avoid generic filler: include meaningful commands/results, a targeted manual scenario, or Not run with a reason.
Use professional Markdown:
Put code, paths, commands, flags, and identifiers in backticks.
Use fenced code blocks for shell transcripts or multi-line examples.
Use GitHub permalinks when citing existing code relevant to the change.
Reference relevant issues or related PRs, but do not reference the PR in its own body.
Suggested PR Body Shape
Use this as a fallback when the repository does not have a PR template:
## Why
Describe the user-facing or maintainer-facing problem, including cause and effect where useful.
## What Changed
Describe the net implementation change in concise prose.Files
- ATTRIBUTION.mdAdded by AutoGineer842 B
- LICENSE.txt10.5 KiB
- SKILL.md6.8 KiB
- agents/openai.yaml273 B
- assets/yeet-small.svg967 B
- assets/yeet.png1.2 KiB
LICENSE.txt
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf of
any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don\'t include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: OpenAI Codex
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.
Needs: Needs a command-line tool
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.
Attribution and licence
- Published by
- OpenAI
- Publisher
- OpenAI (Official)
- Source
- openai/skills · skills/.curated/yeet · commit 49f948f
- Licence
- Apache License 2.0 (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by OpenAI.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download yeet.zip