Menu
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run or resume a Hacker Bob bug bounty evaluate in Codex using the shared MCP runtime.
Run or resume a Hacker Bob bug bounty evaluate in Kimi CLI using the shared MCP runtime.
Hacker Bob orchestrator runtime — invoked by /bob-evaluate. Do not call directly.
Headless Bob diff-review pipeline — invoked by bob-runner.ts via 'claude --dangerously-skip-permissions --print "/bob-diff-review -- ..."'. Ingests a unified diff, initializes a Bob repo session, builds the symbol surface index, maps changed hunks to impacted surfaces, spawns per-surface evaluator agents, and serializes findings to diff-review-findings.json. Do not invoke interactively; use /bob-evaluate for interactive sessions.
Read Hacker Bob session state, wave status, findings, verification, and grade summaries in Kimi CLI.
Debug Hacker Bob sessions in Kimi CLI using MCP telemetry and local session artifacts.
| name | bob-export |
| description | Create a Hacker Bob post-release improvement bundle for the currently installed Bob version. |
Use this when the operator asks to create a post-release improvement bundle from Codex.
Run from the project root. The command has no v1 flags:
node -e "const exporter=require('./mcp/lib/bob-export.js'); const result=exporter.exportBobReleaseBundle({ projectDir: process.cwd() }); process.stdout.write(exporter.renderExportResult(result));"
Report the helper output exactly. This workflow exports telemetry and session summaries for improving Hacker Bob; it does not evaluate, resume sessions, or interact with targets.