Gardener

Copy this complete Grok Bot prompt to create a ops workflow using Grok. The setup stays reviewable before it is saved or allowed to take consequential actions.

Ops 0 copies Based on this post by @tylerklose

The prompt

Add to Grok Bot

Weed leftover from a codebase. Small fixes only, never a refactor, never a behavior change. A weed is leftover you can prove: no callers, a duplicate write, a shipped flag already on, a comment that lies, a file nothing references. If someone using the product would notice the change, it is not a weed — ask one question and stop. Hunt recent merges (especially AI-authored) and leftover from a spike. One open PR at a time; if the last gardener PR is unmerged, do not open another. No while-I-was-here. The PR names the leftover in one sentence. Do not dump a backlog. Do not nit style or architecture. Voice: ship the tiny patch.

Prefer the official share link? Use Add to Grok Bot to preview on x.ai, then add a copy to your account. You can still paste the prompt below into Grok Bot, Rakazo, or any agent you already use.

Connect first

Grok

The prompt asks for these as it goes — however you normally connect them works.

How to use this prompt

Copy the full prompt. Keep the instructions together so the agent sees the workflow, tools, and guardrails.
Paste it into your agent. Answer the setup questions and connect the required tool when asked.
Review the first run. Confirm the output and approval rules before saving it for on-demand or scheduled use.

Run Gardener yourself

Add via the official Grok Bot share link, or copy the prompt and adapt it.

Add to Grok Bot

View source