GitHub CI Integration Workflow Skill

GitHub provider for the findings-pipeline pr-comment producer. The provider surface is exactly TWO pure, zero-LLM verbs — no triage judgment lives here:

• fetch_findings — fetch PR review comments, apply the pre-filter (comment-patterns.json), and file one pr-comment finding per surviving comment via manage-findings add. The untrusted comment body is quarantined under raw_input.{body} (never embedded raw in the top-level detail); the batched manage-findings ingest pass promotes it to top-level only after validate_struct.
• post_responses — apply already-decided triage dispositions back to the PR (a thread-reply carrying the resolution_detail, then a resolve-thread), keyed by each finding's own hash_id.

Both verbs FAIL LOUD when GitHub is not configured (a typed unconfigured status, never a silent no-op). Uses the gh CLI for all GitHub operations.

Architectural context: This SKILL.md owns the producer-side CLI surface. For the producer→store→consumer→gate flow that connects this producer to the unified store, the per-domain ext-triage consumer dispatch, and the invariant gate, see ref-workflow-architecture/standards/findings-pipeline.md.

Enforcement

Execution mode: Two pure provider verbs — fetch_findings files PR review comments to the ledger (untrusted body quarantined under raw_input); post_responses transmits already-decided triage dispositions back to the PR. Triage judgment lives in the consolidated triage pass, NOT in this provider.