yeet
installsforks
How to install yeet?
paulrberg/agent-skills/yeet
$npx -y skills add PaulRBerg/agent-skills --skill yeetUse for GitHub PR/issue/discussion workflows: create/update PRs or issues, post comments, start discussions; triggers include yeet.
SKILL.md
| 1 | # GitHub Contribution Workflows |
| 2 | |
| 3 | Create or update GitHub contributions from repository evidence, using the matching workflow's templates, idempotency |
| 4 | rules, and Paul's writing voice. |
| 5 | |
| 6 | ## Prerequisites |
| 7 | |
| 8 | Use the first required read-only `gh` command in each workflow as authentication validation. The |
| 9 | `scripts/yeet-context.sh` helper is bundled with this skill, not the target repository. Resolve it to an absolute path |
| 10 | relative to the directory containing this `SKILL.md`, and never search for it in the target repository. Prefer the |
| 11 | helper when the workflow needs repository, template, discussion, label, or issue/PR thread context. |
| 12 | |
| 13 | For YAML issue forms, resolve `scripts/issue-form.py` the same way. `inspect` fetches and normalizes the selected live |
| 14 | form; `render` validates answers keyed by field ID and produces the exact Markdown body plus posting metadata. The |
| 15 | helper never selects a template, writes answers or titles, performs privacy review, or posts externally. |
| 16 | |
| 17 | For pull request workflows, also verify: |
| 18 | |
| 19 | - Working tree is clean or changes are committed |
| 20 | - Current branch has commits ahead of the base branch |
| 21 | - Remote tracking is configured |
| 22 | |
| 23 | Use `cli-gh` for GitHub reads, workflow automation, or command syntax that is not part of authoring and posting a |
| 24 | contribution. |
| 25 | |
| 26 | ## Workflows |
| 27 | |
| 28 | Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent. |
| 29 | |
| 30 | | Workflow | Trigger | Reference | |
| 31 | | ----------------- | ------------------------------------------------------ | --------------------------------- | |
| 32 | | Create PR | "create PR", "open PR", "yeet a PR" | `references/create-pr.md` | |
| 33 | | Update PR | "update PR", "edit PR" | `references/update-pr.md` | |
| 34 | | Create Issue | "create issue", "file issue" (generic repo) | `references/create-issue.md` | |
| 35 | | Update Issue | "update issue", "edit issue", "relabel issue" | `references/update-issue.md` | |
| 36 | | Claude Code Issue | "Claude Code issue", "report bug in CC" | `references/issue-claude-code.md` | |
| 37 | | Codex CLI Issue | "Codex issue", "report bug in Codex" | `references/issue-codex-cli.md` | |
| 38 | | Sablier Issue | "Sablier issue", "sablier-labs issue" | `references/issue-sablier.md` | |
| 39 | | Comment on Issue | "comment on issue", "reply on issue", "post a comment" | `references/comment-issue.md` | |
| 40 | | Create Discussion | "create discussion", "start discussion" | `references/create-discussion.md` | |
| 41 | |
| 42 | Each workflow reference links only the shared context, writing, or posting guidance it needs. Post directly when the |
| 43 | user requested creation or update; do not add a confirmation gate. After a failed write, run the linked idempotency |
| 44 | check before any retry. |
| 45 | |
| 46 | Never check an external template attestation unless repository or user evidence verifies it. If a required attestation |
| 47 | or field cannot be verified, ask for that missing fact rather than inventing agreement. Agent-status decoration belongs |
| 48 | outside the authored contribution; add emoji to a PR, issue, discussion, or comment only when the user's content or the |
| 49 | thread's register calls for it. |
| 50 | |
| 51 | ## Completion |
| 52 | |
| 53 | Complete when the requested contribution exists in its final authored state and the returned GitHub URL has been |
| 54 | verified. For updates/comments, report the changed artifact once; for failures, report the idempotency check and next |
| 55 | action without claiming a write succeeded. |
| 56 | |
| 57 | Use `### 🚀 <artifact> created`, `### ✅ <artifact> updated`, or `### ✅ Comment posted`, followed by one Markdown link |
| 58 | containing the repository, number, and title or action. Add a compact field list only when base, draft state, reviewers, |
| 59 | labels, or changed fields matter. On failure, lead with `### ⛔ <artifact> not <action>`, then state the attempted |
| 60 | target, concrete error, idempotency result, and next action. Keep `gh` output, JSON, diagnostics, template fields, URLs, |
| 61 | and authored contribution text exact and undecorated. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
