Skip to content

Commit 90edf18

Browse files
committed
docs: use detected HOL Guard harness
1 parent 6b21729 commit 90edf18

1 file changed

Lines changed: 11 additions & 5 deletions

File tree

skills/hol-guard-vercel/SKILL.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,15 +22,21 @@ If `pipx` is unavailable, do not silently install into the project's Python envi
2222

2323
## Prefer a protected agent runtime
2424

25-
When the current coding agent is one of HOL Guard's supported harnesses, install Guard into that harness and run the agent through Guard so review/approval decisions can happen at the actual tool boundary:
25+
Use HOL Guard's own detection result rather than maintaining a hand-written list of supported harness identifiers:
2626

2727
```bash
28-
hol-guard install <harness>
29-
hol-guard run <harness> --dry-run
30-
hol-guard run <harness>
28+
hol-guard detect --json
3129
```
3230

33-
Supported harnesses include Claude Code, Codex, Copilot CLI, Cursor, Gemini CLI, Hermes, OpenClaw, OpenCode, and Antigravity. Use `hol-guard detect --json` when the active harness is unclear.
31+
If detection reports a supported local coding-agent harness, use the exact identifier it returns when installing and launching the protected session so review/approval decisions can happen at the actual tool boundary:
32+
33+
```bash
34+
hol-guard install <detected-harness>
35+
hol-guard run <detected-harness> --dry-run
36+
hol-guard run <detected-harness>
37+
```
38+
39+
If detection reports no supported harness, do not claim the current session is protected and do not guess an adapter name.
3440

3541
## Preflight an exact Vercel command
3642

0 commit comments

Comments
 (0)