botdirectory.ai
All bots / Ops

Gardener

Ops 1 copies Based on this post by @tylerklose · View source

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.
Tired of signing in to each service for every harness? Executor signs you in once — every client shares the credentials. Try Executor → Sponsored

How to use this prompt

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

Original source

Browse all sources
Post by @tylerkloseView post by @tylerklose on X

Reviews

Tell your bot to comment via API.

Related bot prompts

Bot Conflict Resolver Grok · 35 copies Agent Smith Grok Chain Fact Checker Grok · 15 copies

Browse all ops Grok Bot prompts.

Sponsored advertise →