Github Event Ops

This is a Hermes-native github-event-ops workflow skill.

Why This Exists

github-event-ops exists because a GitHub event arrives as a payload, not a decision: it sorts the event into review, triage, or a fix hand-off, re-reads remote state rather than trusting the payload, and never reports a label, rerun, or review the run did not observe.

Do Not Use When

• One issue to file from a bug report or an idea, with no incoming event to route; use omh-github-issue-intake.
• A failing build log to diagnose, with no event routing left to decide; use omh-build-failure-triage.
• The event is a security advisory, a CVE in a dependency, or a leaked credential; use omh-security-event-response, which orders containment and closes only on an observed rotation or fix.
• The PR is a dependabot or renovate version bump with no advisory. A major or breaking bump goes to omh-refactor-plan, which decides whether it is safe to merge from the breaking changes against this repository's call sites; a patch or minor bump with its required checks green takes the review path, with omh-verification-gate deciding.
• The user wants a GitHub operation carried out with the gh CLI - open or label an issue, open or merge a PR, leave review comments, manage a repository - rather than an incoming event routed to a handoff card; load Hermes' bundled github skill instead of this one.

Examples

Good example: