测试与安全

grok-delegate

amelnagdy/deleg…e-skills

Delegate a coding task to the Grok Build CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Grok — phrasings like "have Grok do X", "delegate this to Grok", "run it through Grok", "use Grok Build to implement/fix/refactor", or "have grok CLI do this" — or to run a queue of coding tasks through Grok while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

  • 4336 次安装
  • 2500 星标
  • 收录于

安装命令

npx skills add https://github.com/amelnagdy/delegate-skills --skill grok-delegate

SKILL.md

Grok Delegate

For a trusted repository rejected by Git's ownership check, the relay supports --trust-git-root <exact-worktree-root>. This opt-in affects only relay Git checks, without persistent Git config or Grok permission changes. See dispatch and poll.

You are the orchestrator. This skill lets you hand a bounded coding task to a separate implementer — the Grok Build CLI (grok) — then review what it produced and land it yourself. You write the brief and own the judgment; Grok does the typing under an explicit autonomy profile; you verify and commit.

Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell command and read a file, so it works the same whether you are Claude Code, Cursor, OpenCode with a selected model, or any comparable agent. (It is designed for Claude Code and Cursor; treat other orchestrators as designed-for, not yet proven.)

When NOT to use this

Grok Delegate

For a trusted repository rejected by Git's ownership check, the relay supports --trust-git-root <exact-worktree-root>. This opt-in affects only relay Git checks, without persistent Git config or Grok permission changes. See dispatch and poll.

You are the orchestrator. This skill lets you hand a bounded coding task to a separate implementer — the Grok Build CLI (grok) — then review what it produced and land it yourself. You write the brief and own the judgment; Grok does the typing under an explicit autonomy profile; you verify and commit.

Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell command and read a file, so it works the same whether you are Claude Code, Cursor, OpenCode with a selected model, or any comparable agent. (It is designed for Claude Code and Cursor; treat other orchestrators as designed-for, not yet proven.)

When NOT to use this