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-05-27
- 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
ckm:ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.
ckm:design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
ckm:banner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
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 Codex's capabilities with specialized knowledge, workflows, or tool integrations.