oh-my-hermes

OMH — Oh My Hermes

An opinionated workflow layer for building, shipping, and operating apps — delivered directly to Hermes.

Like Oh My Zsh is to Zsh. You install it once and Hermes becomes genuinely useful for real software projects. Not a chatbot wrapper. Not a prompt pack. A curated set of skills that Hermes loads and runs autonomously — on your VPS, on your laptop, wherever Hermes lives.

---

Use with your coding agent

Copy this and paste it into Claude, Cursor, Copilot, or any coding assistant:

Install Oh My Hermes by running this command:
git clone https://github.com/salomondiei08/oh-my-hermes /tmp/oh-my-hermes
bash /tmp/oh-my-hermes/install.sh

Then read the full workflow documentation at:
https://github.com/salomondiei08/oh-my-hermes

And follow the instructions in INSTALL_FOR_AGENTS.md in that repo.

---

The core idea

Tell Hermes what you want to build. It helps understand it, designs it, builds it, checks it, ships it, watches it, and learns from real use.

Understand -> Design -> Build -> Check -> Ship -> Learn

The CTO coordinates seven focused agents through Hermes Kanban. GitHub issues and PRs are useful delivery evidence, but they are not the roadmap or the goal. Work can start from an idea, customer feedback, production logs, analytics, or an issue.

Hermes reads the project before asking anything. It asks at most three useful questions, supplies recommended defaults, and continues when you skip them. Only irreversible actions such as production release, rollback, public posting, licensed media, payment, or destructive account changes require your approval.

Founder
  |
  v
CTO: lifecycle, roadmap, delegation, decisions
  |
  +-- Product: brief, priorities, positioning, SEO, content
  +-- Designer: UX, visual verification, launch assets and video
  +-- Builder: working product increments
  +-- Reviewer: journeys, visual/accessibility checks, PR review
  +-- Security: release risk plus daily/weekly assessment
  +-- Ops: deploy, health, deduplicated logs, incidents
  |
  v
Hermes Kanban + memory + cron + completion evidence

Claude Code and Codex remain optional implementation engines. Computer Use is a guarded shared skill for native or authenticated GUI tasks, not another agent. HyperFrames launch videos and licensed music activate only when requested.

---

Get started

Step 1 — Install Hermes Agent

Follow the Hermes quickstart. At the end you have a bot you can message on Telegram (or Slack, Discord, WhatsApp).

Step 2 — Install Oh My Hermes

git clone https://github.com/salomondiei08/oh-my-hermes /tmp/oh-my-hermes
bash /tmp/oh-my-hermes/install.sh

curl | bash is supported too; the installer self-clones a temporary copy when repo files are not present.

Step 3 — Message your bot

set up the CTO loop

The bot inspects the project, asks only for missing settings that matter, and continues with sensible defaults when you skip them. GitHub and a production URL can be connected later; they do not block product discovery and building.

What you unlock at each step:

Step	What to do	What you get
1	Install Hermes + connect Telegram	A bot you can message
2	Run install.sh	36 skills and 6 workflows loaded
3	Message: "set up the CTO loop"	Bot guides the full setup in chat
4	Connect GitHub when useful	Issues and PR delivery enabled
5	Add production URL after deploy	Health and log observation enabled
6	/goal command	Agent stays focused across long sessions
—	Autonomous from here	Product review, daily report, recurring security and logs

---

Skills

Skill	What Hermes does
onboarding	Infers setup, asks at most three optional questions, avoids duplicate crons
clarify-requirements	Reads first, asks only material questions, continues with defaults
product-brief	Writes the compact product source of truth and acceptance criteria
design-handoff	Designer creates DESIGN.md and verifies implemented UI
computer-use	Safely operates native/authenticated GUI only when simpler tools cannot
product-marketing	Positioning, website copy, SEO, launch strategy, and content schedule
creative-production	Product assets and HyperFrames launch video with licensed music evidence
generate-with-seedance	Approved paid video shots through the official Volcengine Ark API
publish-with-buffer	Dry-runs and schedules approved posts with the official Buffer CLI
project-switch	Switches product context without mixing repo, URL, logs, or approvals
project-status	Founder-readable status for gateway, model, project, crons, integrations
failure-recovery	Saves failed cron/agent context to dead-letter logs and alerts the founder
server-bootstrap	Sets up a fresh server with Hermes, Telegram, Oh My Hermes, and CTO loop
ship-this-idea	Runs the flagship idea → brief → design → build → verify → ship flow
reset-runtime	Backs up and clears stale Hermes runtime state without deleting credentials
create-skill	Creates a new skill in the correct format (meta-skill)
choose-engine	Routes tasks to Hermes, Claude Code, or Codex
implement-with-claude-code	Scaffolds Claude Code with full context + scope constraints
implement-with-codex	Scaffolds Codex for targeted single-file fixes
deploy-to-vercel	Pre-deploy checks → deploy → capture URL
connect-supabase	Links Supabase, pushes migrations, sets Vercel env vars
setup-monitoring	Configures Sentry + Uptime Kuma
health-check	Calls /api/health, validates response, checks Supabase + Vercel logs
send-notification	Sends Slack webhook with deployment or status info
post-deploy-followup	Health check + deployment log + notification + summary
manage-github-issues	Triage, create, label, assign, and close GitHub issues
create-github-pr	Creates PR with secret scan before opening
auto-issue-triage	Hourly: scores open issues, picks top priority, starts work
review-github-pr	Verifies the product increment, then approves or requests changes
security-review	Tool-backed release gate plus daily and weekly assessments
await-merge-approval	Founder chooses YES, NO, CLOSE, or LATER
observe-logs	Deduplicates runtime errors and escalates only actionable changes
kanban-task	Creates and updates Hermes kanban cards at every stage
cto-status-report	Daily morning report: what's in progress, done, blocked
backup-hermes-data	Tarballs ~/.hermes/ to S3, Dropbox, or local
rollback	Rolls back Vercel production to previous deploy after health check failure — requires founder YES

---

Agents

Seven agents cover the product lifecycle without creating a profile for every tool. Role definitions live in agents/. Running scripts/setup-cto.sh (or messaging "set up the CTO loop") creates all seven profiles.

---

CTO — Product Lifecycle

The main Hermes session owns the roadmap loop from understanding through learning. It delegates specialists and is the only agent that summarizes decisions to you.

What triggers it: Every hour via cron, or when you send a message.

What it does:

• Watches the kanban continuously (hermes kanban watch)
• Spawns Product, Designer, Builder, Reviewer, Security, or Ops as needed
• Sends you a daily morning report (what shipped, what's stuck, what needs your input)
• Escalates to you only when a human decision is needed — health check failure, task blocked twice, secret found in a diff, scope change
• Makes the call when two sub-agents conflict

What it does NOT do: Replace specialist work or ask for routine decisions.

---

Product (pm) — Product and Growth

Owns product clarity, priorities, positioning, SEO, launch strategy, and growth learning. The profile ID remains pm for compatibility.

What triggers it: When new issues appear on GitHub or when the CTO spawns it for triage.

What it does:

• Reads product evidence, customer feedback, analytics, and issues
• Writes compact briefs and testable outcome tasks
• Asks at most three questions and uses recommended defaults when skipped
• Creates website, SEO, launch, and content plans from real product evidence
• Pings you after 24h if a blocked or approval-waiting card has gone stale

What it does NOT do: Implement code, design assets, invent evidence, or publish externally without approval.

---

Designer — Product and Creative Design

Owns UX, visual direction, responsive behavior, design verification, and launch media.

What it does:

• Writes DESIGN.md from the product brief and existing interface
• Provides a recommended reversible direction instead of blocking on preferences
• Inspects real mobile and desktop renders
• Uses browser tools first and guarded Computer Use only for native/authenticated UI
• Produces restrained HyperFrames launch videos when requested
• Shortlists licensed music and records license coverage before use

What it does NOT do: Hide the product behind synthetic visuals, use unlicensed music, or publish assets without approval.

---

Builder (dev) — Software Builder

Builds the smallest complete product increment and reports acceptance-criteria, test, runtime, and change evidence.

What triggers it: When the PM Agent creates a ready card assigned to dev and the dispatcher starts work.

What it does:

• Claims the highest-priority ready ticket assigned to dev
• Chooses the right engine for the task: Hermes terminal for ops/config, Codex for single-file bug fixes, Claude Code for multi-file features
• Implements the change, commits after every logical unit of work
• Never commits .env files, API keys, tokens, or credentials — scans git diff --staged before every commit
• Creates a PR when the repository uses that delivery workflow
• Completes the implementation task with PR summary and metadata for Security/QA handoff

What it does NOT do: Merge PRs, deploy to production, start a second ticket while one is in progress, or make product decisions.

---

Security — Product Security

Independently reviews relevant release risk and runs recurring assessment.

What triggers it: Security-relevant changes, daily lightweight cron, and weekly deeper assessment.

What it does on every PR:

• Uses available Gitleaks, Semgrep, OSV-Scanner, and ecosystem audits
• Reviews auth, authorization, input, uploads, payments, logs, and RLS in context
• Deduplicates findings and requires evidence plus a re-test

What it does regularly: Daily secret/Critical advisory checks and a weekly full dependency, configuration, and supply-chain assessment.

Severity table:

Level	Action
Critical	Block merge. Alert you immediately via Telegram.
High	Block merge. Comment on PR with fix instructions for Dev.
Medium	Comment on PR. Fix before next sprint. Does not block.
Low	Log to memory. Include in weekly report.

What it does NOT do: Run destructive tests on production, silently accept risk, or claim an unavailable scanner passed.

---

Reviewer (qa) — Product Quality