Omh Github Event Ops

CommunityPopular

rlaope

omh-github-event-ops

[omh] Hermes GitHub event operations workflow: route PR, issue, CI, and review webhook events into triage, review, or fix handoff cards. Use when the user says: github-event-ops, github event ops, github ops, github triage, github pr, github review, github action, github actions.

Overview

Publisher	rlaope
Repository	`oh-my-hermes`
Skill name	`omh-github-event-ops`
Stars	2.7K
Forks	194
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by rlaope on GitHub. Read the source before you install it.

Installation

Install the Omh Github Event Ops AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git /tmp/oh-my-hermes
mkdir -p .claude/skills
cp -r /tmp/oh-my-hermes/agent-skills/omh-github-event-ops .claude/skills/omh-github-event-ops

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Omh Github Event Ops in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Omh Github Event Ops on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Omh Github Event Ops is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Github Event Ops

This is an OMH github-event-ops workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

github-event-ops exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.

Do Not Use When

The request is already handled by a narrower explicit skill with stronger evidence.
The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.

Examples

Good example:

Prompt: github-event-ops PR opened with failing CI; triage whether this needs review or fix handoff.
Expected behavior: Produce prepare_github_event_ops_card with required context, wrapper actions, and not-evidence boundaries.
Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.

Bad example:

Prompt: github-event-ops prove the issue was labelled and CI was rerun.
Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.

Completion Checklist

Confirm the workflow target, evidence boundary, and stop condition are named.
Report which outputs are prepared, observed, blocked, or missing.
Name the smallest next verification or handoff instead of claiming completion from narration.

Recovery Notes

If required context is missing, ask one blocking question or route back to the narrower workflow.
If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.

Use When

Use when Hermes receives or is asked to reason about GitHub PR, issue, review, or CI events and must choose review, triage, or fix-handoff without claiming a bot ran.


Strong routing signals: `github-event-ops`, `github event ops`, `github ops`, `github triage`, `github pr`, `github review`, `github action`, `github actions`, `pr opened`, `pull request opened`, `pull request review`, `pr review`, `ci failed`, `check failed`, `checks failed`, `failing checks`, `issue opened`, `issue triage`, `pull request webhook`, `github webhook`, `github issue`, `github issue to pr`, `auto review pr`, `label issue`, `label pr`, `ci analysis`, `fix handoff`, `review handoff`, `깃허브`, `깃허브 pr`, `깃허브 이슈`, `github issue 들어온`, `이슈 라벨`, `pr 리뷰`, `리뷰 라벨`, `픽스 핸드오프`, `ci 실패`

Catalog Metadata

Category: github-ops Phase: event-routing Quality tier: workflow-surface-gated Reasoning demand: standard

Quality bar:

Name the user-facing workflow objective, required context, next action, and stop condition.
Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
Expose missing tools, credentials, targets, or observations as user-visible gaps.

Required inputs:

user request
target context
delivery or status expectation
known missing evidence

Expected outputs:

github-event-ops/v1 card or guidance
next action
prepared-vs-observed boundary

Artifact expectations:

github-event-ops/v1 metadata-only runtime or wrapper card when recorded

Safety rules:

A GitHub event ops card is not webhook delivery, GitHub API mutation, review completion, label application, CI rerun, or fix execution evidence. When a fix is owned by Hermes coding, read hermes_coding_harness/v1 before reporting build, review, CI, PR, or merge state.
Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.

Runtime Evidence

Use the current host's own tools and subagent/task mechanism when available; otherwise run the same lanes sequentially or name the unavailable capability. A prepared plan, handoff, checklist, or skill installation is not execution, review, CI, merge-readiness, or merge evidence. Report actual tool results or not_observed / not_available; never invent dispatch or host accounting. Treat supplied context as advisory, not proof of hidden memory reads or writes. State scope, constraints, verification, and the stop condition before work. Supporting paths are relative to this skill directory; sibling skill paths are relative to its parent. Resolve them from the host-provided skill base directory ({baseDir} on hosts that provide it), never a hardcoded install location. A named workflow not installed here is unavailable, not permission to emulate its host-specific capabilities. Verify through the real surface before done.

Frequently asked questions

What does the Omh Github Event Ops AI skill do?

Why use Omh Github Event Ops on TypingMind?

Because you install it once and use it with any model. Omh Github Event Ops is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Omh Github Event Ops in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rlaope/oh-my-hermes/tree/main/agent-skills/omh-github-event-ops. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Omh Github Event Ops?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Omh Github Event Ops?

As many as you like. As long as a model supports skills, you can use Omh Github Event Ops with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Omh Github Event Ops AI skill free?

Yes. It is published on GitHub by rlaope under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Jpa Patterns

affaan-m

CommunityPopular

Patrones JPA/Hibernate para diseño de entidades, relaciones, optimización de consultas, transacciones, auditoría, indexación, paginación y pooling en Spring Boot.

Kotlin Patterns

Patrones idiomáticos de Kotlin, buenas prácticas y convenciones para construir aplicaciones Kotlin robustas, eficientes y mantenibles con coroutines, null safety y builders de DSL.

Kotlin Testing

Patrones de pruebas Kotlin con Kotest, MockK, pruebas de coroutines, pruebas basadas en propiedades y cobertura con Kover. Sigue la metodología TDD con prácticas idiomáticas de Kotlin.

Laravel Patterns

Patrones de arquitectura Laravel, routing/controladores, Eloquent ORM, capas de servicio, colas, eventos, caché y API resources para aplicaciones en producción.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Github Event Ops

Why This Exists

Do Not Use When

Examples

Completion Checklist

Recovery Notes

Use When

Catalog Metadata

Runtime Evidence

Frequently asked questions

Related AI Skills

Set up your own AI workspace now