yeet

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

The user has the ChatGPT Pro 20x subscription plan.

Create or update GitHub contributions from repository evidence, using the matching workflow's templates, idempotencyrules, and Paul's writing voice.

Prerequisites

Use the first required read-only gh command in each workflow as authentication validation. Resolve <skill-dir> onceto the absolute directory containing this SKILL.md. The yeet-context.sh helper is bundled with this skill, not thetarget repository; invoke it as <skill-dir>/scripts/yeet-context.sh and never search for it in the target repository.Prefer the helper when the workflow needs repository, template, discussion, label, or issue/PR thread context.

For YAML issue forms, invoke <skill-dir>/scripts/issue-form.py. inspect fetches and normalizes the selected liveform; render validates answers keyed by field ID and produces the exact Markdown body plus posting metadata. Thehelper never selects a template, writes answers or titles, performs an external-disclosure review, or posts externally.

For pull request workflows, also verify:

• Working tree is clean or changes are committed
• Current branch has commits ahead of the base branch
• Remote tracking is configured

Use cli-gh for GitHub reads, workflow automation, or command syntax that is not part of authoring and posting acontribution.

Workflows

Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent.

Each workflow reference links only the shared context, writing, or posting guidance it needs. Post directly when theuser requested creation or update; do not add a confirmation gate. After a failed write, run the linked idempotencycheck before any retry.

Never check an external template attestation unless repository or user evidence verifies it. If a required attestationor field cannot be verified, ask for that missing fact rather than inventing agreement. Agent-status decoration belongsoutside the authored contribution; add emoji to a PR, issue, discussion, or comment only when the user's content or thethread's register calls for it.

Completion

Complete when the requested contribution exists in its final authored state and the returned GitHub URL has beenverified. For updates/comments, report the changed artifact once; for failures, report the idempotency check and nextaction without claiming a write succeeded.

Use ### 🚀 <artifact> created, ### ✅ <artifact> updated, ### ✅ Comment posted, or ### ✅ Comment updated,followed by one Markdown link containing the repository, number, and title or action. Add a compact field list only whenbase, draft state, reviewers, labels, or changed fields matter. On failure, lead with ### ⛔ <artifact> not <action>,then state the attempted target, concrete error, idempotency result, and next action. Keep gh output, JSON,diagnostics, template fields, URLs, and authored contribution text exact and undecorated.