production-audit
starsforks
How to install production-audit?
rlaope/oh-my-hermes/production-audit
$npx -y skills add rlaope/oh-my-hermes --skill production-audit[omh] Hermes Production Audit workflow: evaluate release, deploy, security, observability, rollback, docs, and support readiness without claiming production access.
SKILL.md
| 1 | # Production Audit |
| 2 | |
| 3 | This is a Hermes-native `production-audit` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `production-audit` gives OMH a preflight release surface so operators can see production risks before launch while OMH stays out of deploy and infrastructure execution. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user wants to implement a feature or fix; prepare a coding handoff first. |
| 12 | - The user wants incident/SLO analysis after production behavior; use `reliability-review`. |
| 13 | - The user wants a narrow code diff review; use `code-review`. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: production-audit 이 릴리즈가 운영에 나가도 되는지 테스트, CI, 롤백, 모니터링 기준으로 봐줘. |
| 20 | - Expected behavior: Prepare readiness_matrix/v1, release_gate_verdict/v1, rollback_and_monitoring_plan/v1, and missing-evidence list. |
| 21 | - Why: The request is release-readiness review, not implementation or deploy execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: production-audit 지금 바로 prod 배포하고 정상이라고 말해줘. |
| 26 | - Expected behavior: Block deploy/health claims without observed operator evidence and route deploy to an explicit authorized workflow. |
| 27 | - Why: Production audit can assess readiness, but it cannot secretly deploy or observe live health. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Findings or no-issue results are grounded in concrete file, artifact, command, or source evidence. |
| 32 | - Open questions, residual risk, and missing verification are named. |
| 33 | - Fixes or follow-up work are separate handoffs unless the user explicitly asked to implement them. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If the reviewed target is missing, inspect the requested artifact or ask one target question. |
| 38 | - If independent verification is unavailable, report the gap and avoid an approval-style claim. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use before launch, deploy, release, or public delivery when Hermes should check operational readiness and expose missing production evidence. |
| 55 | |
| 56 | Strong routing signals: `production-audit`, `production audit`, `production readiness`, `prod audit`, `prod readiness`, `ready for production`, `ready to ship`, `ship readiness`, `release readiness`, `launch readiness`, `preflight audit`, `operational readiness`, `rollback readiness`, `프로덕션 준비`, `출시 준비`, `운영 준비`, `릴리즈 준비`, `롤백 준비` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `review` |
| 61 | Phase: `production-readiness` |
| 62 | Hermes role: `reviewer` |
| 63 | Quality tier: `production-readiness-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name scope, environment, release channel, owners, and acceptable risk threshold. |
| 68 | - Check build/test/CI, security/privacy, performance, observability, rollback, docs/support, and release communication. |
| 69 | - Return GO, HOLD, or BLOCK only with evidence IDs and missing evidence. |
| 70 | - Convert remediation into explicit follow-up workflows instead of silently patching. |
| 71 | |
| 72 | Handoff policy: |
| 73 | |
| 74 | Keep readiness synthesis in Hermes. Code fixes, deploys, infrastructure changes, security scans, and platform actions require selected executor/runtime or operator evidence. |
| 75 | |
| 76 | Required inputs: |
| 77 | |
| 78 | - product, service, release, or artifact scope |
| 79 | - target environment and release channel |
| 80 | - known test, CI, deploy, observability, security, and support evidence |
| 81 | - rollback owner and acceptable risk threshold |
| 82 | |
| 83 | Expected outputs: |
| 84 | |
| 85 | - production_audit_plan/v1 |
| 86 | - readiness_matrix/v1 |
| 87 | - release_gate_verdict/v1 |
| 88 | - rollback_and_monitoring_plan/v1 |
| 89 | - |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
