القائمة
Use when fixing broken automation (CI, gates, hooks). A commit is NOT a fix; verify the fix is active post-deploy; restart gateway after config.yaml changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Token-efficient second opinion slash command /advice. Extracts decision point + artifact (≤150 lines), then fans out in parallel: (1) Opus subagent reviewer with fallback chain codex→agy→cursor, (2) /research on the decision topic, (3) /secondo multi-model opinion. Use instead of advisor() which ships the full conversation uncached.
Lazy senior-dev mode — the seven-rung ladder that decides whether to write code at all, whether to reuse code that already exists, and whether to prefer stdlib/platform/installed deps over a new dependency. Use before writing any code, every PR diff, every fix, every feature. Source attribution included.
Use when making any "X is enabled" / "feature X works" / "cache works" claim in a running session — requires runtime probe output from the standard harness startup path, NOT a launchd/cron test that explicitly sets the activation env var.
Pre-flight checklist for self-hosted runner failures. Use when investigating low disk, missing runner, or stuck Green Gate on the jleechanorg/worldarchitect.ai fleet. Always verifies host-level container state, not just GitHub API.
When asked to verify whether a Claude Code feature works (especially slash commands, dialogs, pickers, status indicators), spawn a real interactive TUI session in cmux — never use `claude --print "/feature"` as a test, because --print is non-interactive and will always return "isn't available in this environment" regardless of whether the feature actually works.
Read ~/.hermes/agent-orchestrator.yaml BEFORE declaring an --agent <X> value unsupported. Lists plugin shorthands (wafer, minimax, agy).
| name | fix-completion-deploy |
| description | Use when fixing broken automation (CI, gates, hooks). A commit is NOT a fix; verify the fix is active post-deploy; restart gateway after config.yaml changes. |
When fixing broken automation (skeptic gate, CI workflows, lifecycle workers, hooks):
git push, report the exact pushed HEAD SHA and the remote commit URL, preferably https://github.com/<owner>/<repo>/commit/<sha>.Config changes also require deployment — a config file write with no process restart is a silent no-op:
config.yaml, restart the gateway immediately (see ~/.hermes/CLAUDE.md post-mutation section for the exact sequence)curl /health (liveness ≠ config loaded)~/.hermes/config.yaml (staging) and ~/.hermes_prod/config.yaml (prod) must be updated; they don't sync automaticallyWhy: 2026-06-02 — M3 model switch wrote config files correctly but skipped gateway restart. Process ran with M2.7 in memory for 4 days. Skeptic bug precedent: fix was in commits but not deployed for hours.