grok
Grok starting point for Claude Code: route/nextAction, status dashboard, worktree, subscription-safe delegate — full /grok:* surface.
Plugin grok from marketplace grok-marketplace in xzawed/claude-grok-build-plugin. Commands read from the repo's manifest — 8 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (4)
maintainer-preflightUse before claiming work is done, before committing, and before opening a PR in this repo — runs the mcp-server test/typecheck/build gates and the committed-bundle rule. Trigger on "done", "ready to commit", "open a PR", or any completion claim.
repo-scopeUse when anyone asks what to work on next in this repo — "what's next", "anything left", "is there remaining work", "next task" — or before opening any PR the owner did not explicitly request. Enforces the docs/09 scope rule, whose default answer is: no work.
grok-first-mileOnboarding and first-session guidance for the Grok Claude Code plugin. Use when the user is new to the plugin, asks how to use Grok, wants a tour, setup help, or what to try first — or when they just installed the plugin and need a clear starting path.
grok-routingWhen to delegate coding work to Grok Build vs handle it in Claude. Use whenever the user asks for bulk edits, test backfill, migrations, boilerplate, exploratory prototypes, or whether to use /grok:delegate — and when reviewing whether a task is safe to hand to Grok.
Slash commands (27)
/grok:boilerplateScaffold boilerplate with Grok (preset)
/grok:cliRun any Grok CLI command (passthrough)
/grok:delegateDelegate a coding task to Grok
/grok:exportExport a Grok session transcript as Markdown
/grok:importWhy Grok has no session import (use /grok:sessions + /grok:resume)
/grok:inspectShow the configuration Grok discovers for this directory
/grok:loginSign in to Grok (guides the one-time terminal login)
/grok:logoutSign out of Grok and clear cached credentials
/grok:mcpManage Grok's MCP server configurations
/grok:memoryManage Grok cross-session memory
/grok:migrateApply a mechanical migration pattern with Grok (preset)
/grok:modelsList available Grok models
/grok:planGrok plan preview — reads files; the shell, edits and MCP tools are denied, scheduled and background tools removed
/grok:resumeContinue a prior Grok session (multi-turn resume)
/grok:reviewReview Grok output (diff gate — never auto-commit)
/grok:routeRecommend Claude vs Grok for a task (no execution)
/grok:sessionsList, search, or delete Grok sessions (no restore — use /grok:resume)
/grok:setupVerify Grok is installed and signed in; guide setup
/grok:statusDashboard — auth ready, billing, usage, last session
/grok:testsBackfill or expand tests with Grok (preset)
/grok:tour15-minute guided tour — prove Grok works in this Claude session
/grok:traceExport a Grok session trace locally, or upload it to xAI
/grok:updateCheck for a Grok update, or install one
/grok:usageShow Grok delegation usage summary (counts, billing, recent)
/grok:verifyDelegate a task to Grok with a self-verification loop
/grok:versionShow the installed Grok version
/grok:worktreeList, diff, apply, remove, or prune Grok isolation worktrees
Subagents (1)
grok-workerExecute bulk, repetitive, low-risk, or narrow coding tasks via Grok Build MCP tools (tests backfill, migrations, boilerplate, mechanical refactors). Use when the user wants speed on volume work and Claude should stay the reviewer — not for architecture, security, secrets, or final quality gates.
MCP servers (1)
grok-buildruns: node ${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/index.js
Hooks (1)
- PreToolUse
node "${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/hook.js"
Maintain grok?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.