Agent Skills
› ruvnet/metaharness
› validate-harness
validate-harness
GitHub一键执行5项发布就绪检查:doctor、verify、path-guard、mcp配置及GCP密钥验证,任一失败则退出。
触发场景
用户请求验证harness的发布准备状态
需要运行完整的发布前检查清单
安装
npx skills add ruvnet/metaharness --skill validate-harness -g -y
SKILL.md
Frontmatter
{
"name": "validate-harness",
"description": "Release-readiness umbrella check for a scaffolded harness — runs doctor, witness verify, hardcoded-path scan, MCP server config, and GCP Secret Manager validation in one shot. Exits non-zero if any sub-check fails."
}
validate-harness
Codex skill that runs the 5 release-readiness gates from
harness validate.
What it checks
| # | Check | What it does |
|---|---|---|
| 1 | doctor |
File shape + manifest sha256 + at-least-one host artifact |
| 2 | verify |
Witness manifest signature (Ed25519) — skipped if no witness yet |
| 3 | path-guard |
Scans your TS/JS/Rust files for hardcoded /tmp/, C:\, /Users/, /home/ — the original Windows /tmp bug regression class |
| 4 | mcp |
.mcp/servers.json entries have name + command |
| 5 | secrets |
gcloud auth list + project + NPM_TOKEN exist in GCP Secret Manager |
Each check reports PASS / FAIL / WARN with a one-line detail. Exits 1 if any FAIL.
Usage from Codex
/validate-harness
/validate-harness path=./my-harness
/validate-harness path=./my-harness skip_gcp=true
/validate-harness secret=NPM_TOKEN_DEV
Equivalent CLI
harness validate ./my-harness --skip-gcp --secret=NPM_TOKEN_DEV
Why this exists
Before iter 20, you needed to remember to run harness doctor, harness verify, harness secrets check, and node scripts/path-guard.mjs separately. This is the single release-readiness gate.
版本历史
- 6e1902b 当前 2026-07-05 11:03


