GH Workflow

Use the canonical GitHub operations lane for issue, PR, review, CI, and merge work driven by gh. This skill acts on GitHub state and includes GitHub-native readiness checks (checks, review-thread signal, mergeability), but it does not replace external governance systems. Boundary: this skill executes end-to-end gh/git lifecycle operations with post-mutation verification, while connector-first GitHub triage/routing stays upstream.

Standards snapshot (March 2026)

• Keep GitHub operations evidence-backed and stateful: know the repo, branch, PR, and current git status before acting.
• Verify every git-changing operation immediately after it happens.
• Prefer one explicit mode at a time unless the user clearly wants the full lifecycle.
• Treat non-GitHub-Actions providers as link-only evidence unless a narrower skill owns them.
• Keep GitHub Actions workflows pinned to full commit SHAs for third-party actions and use least-privilege permissions.

Philosophy

• GitHub state and local git state must agree before you call work complete.
• Prefer explicit operating modes over fuzzy all-in-one execution.
• Verification after mutation is part of the workflow, not an optional epilogue.