verify

name	verify
description	Have Grok independently verify a change in an existing worktree (no source edits, hermetic)
argument-hint	--worktree <absolute-path> (--task <text> | --task-file <path>) [--model <id>] [--timeout <s>] [--max-turns <n>]
allowed-tools	Bash(node:*)

How to run (transparent)

1. Take the absolute Base directory for this skill from the Skill tool (the folder that contains this skill's SKILL.md and run.mjs).
2. Set SKILL_BASE to that path. Do not invent versioned cache paths.
3. Always invoke the companion only through this skill's runner:

SKILL_BASE='<Base directory for this skill - absolute path from Skill tool>'
# Required for completion notifications (plugin/references/execution-context.md):
export GROK_COMPANION_EXECUTION_CONTEXT=foreground   # or background
node "$SKILL_BASE/run.mjs" <mode> [args...]

run.mjs finds the plugin install from its own location and runs scripts/grok-companion.mjs. No CLAUDE_PLUGIN_ROOT / PLUGIN_ROOT required.

If the host already exported CLAUDE_PLUGIN_ROOT or PLUGIN_ROOT, you may call node "$CLAUDE_PLUGIN_ROOT/scripts/grok-companion.mjs" instead; prefer "$SKILL_BASE/run.mjs" whenever the Skill tool loaded this skill.

Return companion stdout verbatim. Never put free-text in --task "..."; use --task-file - with a single-quoted heredoc.

Run a Grok verify through the hardened wrapper and relay its result envelope. verify inspects and tests a change in an EXISTING worktree (typically one a prior code run produced), has no source-editing tools, and always ends with a machine-readable pass / fail / inconclusive verdict plus evidence.

Raw slash-command arguments: $ARGUMENTS

Required wrapper flags (copy exactly, substitute only placeholder values):

• --worktree <absolute-path-to-worktree> is required.
• Exactly one of --task <text> or --task-file <path> is required.
• Preserve the user's arguments exactly. Do not strip, add, or reorder flags. Do not invent a flag that is not in the argument-hint.
• Injection safety (canonical rationale: plugin/references/argv-safety.md): task text is NEVER placed in a shell-evaluated position - deliver it with --task-file - and a SINGLE-QUOTED heredoc. Wrap every substituted flag VALUE in single quotes (--target '<path>'). Bare flags (--web) carry no value to quote.

NO web access:

• verify NEVER accepts --web - independent verification stays hermetic by design. If the user asks for --web on a verify run, do NOT add it; explain that verify is hermetic and offer reason --web or review --web instead.

Run it as one Bash call and relay the result. When the arguments carry a --task <text>, route that text through STDIN so it is never shell-evaluated:

export GROK_COMPANION_EXECUTION_CONTEXT=foreground
node "$SKILL_BASE/run.mjs" verify --worktree '<worktree from $ARGUMENTS>' [other non-task flags from $ARGUMENTS, each substituted value single-quoted] --task-file - <<'GROK_TASK'
<the --task text from $ARGUMENTS, verbatim>
GROK_TASK

When the arguments already use --task-file <path>, drop the heredoc and pass every flag as single-quoted argv tokens:

export GROK_COMPANION_EXECUTION_CONTEXT=foreground
node "$SKILL_BASE/run.mjs" verify --worktree '<worktree from $ARGUMENTS>' --task-file '<path from $ARGUMENTS>' [other non-task flags from $ARGUMENTS, each substituted value single-quoted]

• Return the command stdout envelope VERBATIM. Do not paraphrase, summarize, or add commentary before or after it. Preserve the exit status. The verdict lives in the envelope's verifier.verdict; do not restate it as your own conclusion in place of the raw envelope.

If the companion prints an actionable "could not locate the Grok wrapper" message instead of an envelope, tell the user to run /grok:setup.