yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- yeet
- description
- Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
02 资源文件 4
- 参考文档agents/openai.yaml298 B
- 资产文件assets/yeet-small.svg967 B
- 资产文件assets/yeet.png1.2 KB
- 许可证LICENSE.txt10.5 KB
03 SKILL.md 正文
GitHub Publish Changes
Overview
Use this skill only when the user explicitly wants the full publish flow from the local checkout: branch setup if needed, staging, commit, push, and opening a pull request.
This workflow is hybrid:
- Use local
gitfor branch creation, staging, commit, and push. - Prefer the GitHub app from this plugin for pull request creation after the branch is on the remote.
- Use
ghas a fallback for current-branch PR discovery, auth checks, or PR creation when the connector path cannot infer the repository or head branch cleanly.
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. - Require a local git repository with a clean understanding of which changes belong in the PR.
Naming conventions
- Branch:
codex/{description}when starting from main/master/default. - Commit:
{description}(terse). - PR title:
[codex] {description}summarizing the full diff.
Workflow
- Confirm intended scope.
- Run
git status -sband inspect the diff before staging. - If the working tree contains unrelated changes, do not default to
git add -A. Ask the user which files belong in the PR.
- Run
- Determine the branch strategy.
- If on
main,master, or another default branch, createcodex/{description}. - Otherwise stay on the current branch.
- If on
- Stage only the intended changes.
- Prefer explicit file paths when the worktree is mixed.
- Use
git add -Aonly when the user has confirmed the whole worktree belongs in scope.
- Commit tersely with the confirmed description.
- Run the most relevant checks available if they have not already been run.
- If checks fail due to missing dependencies or tools, install what is needed and rerun once.
- Push with tracking:
git push -u origin $(git branch --show-current). - Open a draft PR.
- Prefer the GitHub app from this plugin for PR creation after the push succeeds.
- Derive
repository_full_namefrom the remote, for example by normalizinggit remote get-url originor by usinggh repo view --json nameWithOwner. - Derive
head_branchfromgit branch --show-current. - Derive
base_branchfrom the user request when specified; otherwise use the remote default branch, for example viagh repo view --json defaultBranchRef. - If the branch is being pushed from a fork or the PR target differs from the remote that was just pushed, prefer
gh pr createfallback because the connector PR creation flow expects one repository target and may not encode cross-repo head semantics cleanly. - If connector-based PR creation cannot infer the repository or branch cleanly, fall back to
gh pr create --draft --fill --head $(git branch --show-current). - Write the PR body to a temp file with real newlines when using CLI fallback so the markdown renders cleanly.
- Summarize the result with branch name, commit, PR target, validation, and anything the user still needs to confirm.
Write Safety
- Never stage unrelated user changes silently.
- Never push without confirming scope when the worktree is mixed.
- Default to a draft PR unless the user explicitly asks for a ready-for-review PR.
- If the repository does not appear to be connected to an accessible GitHub remote, stop and explain the blocker before making assumptions.
PR Body Expectations
The PR description should use real Markdown prose and cover:
- what changed
- why it changed
- the user or developer impact
- the root cause when the PR is a fix
- the checks used to validate it
04 同仓库更多 Skills
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
skill-audit
Pre-install security scanner for AI agent skills. 7.5% of 14,706 skills are malicious. Audit before you trust.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
bumblebee
Run Bumblebee supply-chain inventory and exposure scans on macOS/Linux to detect compromised packages, extensions, and MCP host configs.