GitHub Contribution Workflows

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

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

Prerequisites

Use the first required read-only gh command in each workflow to validate authentication. Resolve <skill-dir> once to the absolute directory containing this SKILL.md.

This skill, rather than the target repository, bundles the yeet-context.sh helper. Invoke it as <skill-dir>/scripts/yeet-context.sh. 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 live form. render validates answers keyed by field ID and produces the exact Markdown body plus posting metadata. The helper never selects a template, writes answers or titles, performs an external-disclosure review, or posts externally. All issue creation and update workflows apply references/context.md > Issue Metadata Permissions before resolving or passing metadata. Rendered template metadata describes requested values, not the viewer's authority to apply them.

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 a contribution.

Workflows

Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent. Then read the shared reference sections that the workflow names (posting.md, writing.md, context.md) in one parallel batch.

Each workflow reference links only the shared context, writing, or posting guidance it needs. Every authored body or comment must follow posting.md > Model Co-signature. When the user requested creation or update, post directly. Do not add a confirmation gate. After a failed write, run the linked idempotency check before any retry.

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

Completion

The workflow is complete when the requested contribution exists in its final authored state and the returned GitHub URL is verified. For updates/comments, report the changed artifact once. Determine the outcome from readback, not the command's exit status: creation can succeed before a metadata mutation fails.

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 when base, draft state, reviewers, labels, or changed fields matter. For verified partial success, report the created or updated artifact and identify omitted or failed metadata.

Use ### ⛔ <artifact> not <action> only for confirmed noncompletion. If readback is inconclusive, report the outcome as unverified. Include the concrete error, idempotency result, and next action. Keep gh output, JSON, diagnostics, template fields, URLs, and authored contribution text exact and undecorated.