|
1 | 1 | --- |
2 | 2 | name: omv |
3 | | -description: oh-my-vul local-first vulnerability research project manager. Shows workspace status, next actions, installed omv-* skills, registry info, and delegates .omv findings lifecycle commands. Use when the user types /omv, asks what to do next, or manages local findings. |
| 3 | +description: oh-my-vul local-first vulnerability research project manager for Pi, Codex, and Claude Code. Shows workspace status, next actions, installed omv-* skills, registry info, and delegates .omv findings lifecycle commands. Use when the user invokes /skill:omv, $omv, or /omv; asks what to do next; or manages local findings. |
4 | 4 | --- |
5 | 5 |
|
6 | 6 | # omv |
7 | 7 |
|
8 | | -oh-my-vul local-first vulnerability research project manager for Codex and Claude Code. |
| 8 | +oh-my-vul local-first vulnerability research project manager for Pi, Codex, and Claude Code. |
| 9 | + |
| 10 | +Invocation depends on the active platform: Pi uses `/skill:omv [args]`, Codex uses `$omv [args]`, and Claude Code uses `/omv [args]`. The command table below uses `/omv` as shorthand for the active platform's project-manager invocation. |
9 | 11 |
|
10 | 12 | **Process first:** For any vulnerability research session (find / audit / report / “what next”), apply `using-omv` discipline — evidence before claims, CLI gates before “confirmed” or “ready to submit”, prefer campaign + attack-surface cards before bulk hypotheses. Do not invent parallel workflows outside `.omv/` + `omv` CLI. |
11 | 13 |
|
@@ -50,16 +52,16 @@ oh-my-vul local-first vulnerability research project manager for Codex and Claud |
50 | 52 | /omv help — show this help text |
51 | 53 | ``` |
52 | 54 |
|
53 | | -The first word after `/omv` is treated as the subcommand. Unknown subcommands show the help text. |
| 55 | +The first word after the platform-specific project-manager invocation is treated as the subcommand. Unknown subcommands show the help text. |
54 | 56 |
|
55 | 57 | ## Skills in This Collection |
56 | 58 |
|
57 | 59 | | Skill | Invocation | Purpose | |
58 | 60 | |---|---|---| |
59 | | -| omv-find | `/omv-find` | Find and rank open-source packages worth auditing | |
60 | | -| omv-audit | `/omv-audit` | Deep-audit a candidate finding, prove or disprove the vulnerability | |
61 | | -| omv-repro | `/omv-repro` | Guide local reproduction, fill evidence.observed_result | |
62 | | -| omv-report | `/omv-report` | Generate VulDB/CVE/GHSA/OSV advisory reports | |
| 61 | +| omv-find | `/skill:omv-find` on Pi; `$omv-find` on Codex; `/omv-find` on Claude Code | Find and rank open-source packages worth auditing | |
| 62 | +| omv-audit | `/skill:omv-audit` on Pi; `$omv-audit` on Codex; `/omv-audit` on Claude Code | Deep-audit a candidate finding, prove or disprove the vulnerability | |
| 63 | +| omv-repro | `/skill:omv-repro` on Pi; `$omv-repro` on Codex; `/omv-repro` on Claude Code | Guide local reproduction, fill evidence.observed_result | |
| 64 | +| omv-report | `/skill:omv-report` on Pi; `$omv-report` on Codex; `/omv-report` on Claude Code | Generate VulDB/CVE/GHSA/OSV advisory reports | |
63 | 65 |
|
64 | 66 | ## Registry |
65 | 67 |
|
@@ -96,7 +98,7 @@ Use `omv help`, `omv help review`, `omv help findings`, `omv help repro`, or `om |
96 | 98 | - `/omv restore <id>` -> `omv findings restore <id>` |
97 | 99 | - `/omv findings ...` -> `omv findings ...` |
98 | 100 |
|
99 | | -**If `omv` is not found on PATH**, output: "`omv` is not installed. Run `npm install --global oh-my-vul`, then `omv setup --platform codex` in Codex or `omv setup --platform claude-code` in Claude Code." |
| 101 | +**If `omv` is not found on PATH**, output: "`omv` is not installed. Run `npm install --global oh-my-vul`. Pi users already have the Skills and should not run `omv setup`; Codex and Claude Code users should then run `omv setup --platform codex|claude-code` for their platform." |
100 | 102 |
|
101 | 103 | ### Subcommand reference |
102 | 104 |
|
|
0 commit comments