Skip to content
BotsDots

Grok Bot template · Coding & Shipping

Gardener

Shared by @tylerklose

Pulls provable dead code in tiny behaviour-preserving pull requests

Add to Grok Bot ↗Share on XRe-check link

What this Grok bot does

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.

— the creator's description on the bot's x.ai share page

Gardener at a glance

Gardener is an on demand coding bot shared by @tylerklose and first listed on 2026-08-28. It works when you message it rather than on a timer, which keeps usage low. 4 independent public catalogs list it, and its x.ai share link was last checked live on 2026-10-20.

How Gardener compares

On our popularity score (installs, votes and how many catalogs list it), Gardener shares rank 128 of 703 Coding & Shipping bots with 88 others. Its description mentions code repos (29% of the category).

The closest alternatives in the catalog, and how each differs from Gardener
BotWhat it doesSchedule · accessCompared with Gardener
Claude Code Bot@carlosnoriegaMoves your bot's code work from Cursor cloud agents to Claude CodeOn demandConnects accountsBoth cover code. It also connects to GitHub, Cursor.
Liquid Code ReviewerGustavoLiquid code security review by Zero Agency, with linked onboarding and code-review playbooksOn demandConnects accountsBoth cover code. Same schedule and access level.
T3 Code Bridge@trevinBridges Grok Bot and T3 CodeOn demandLow accessBoth cover code. It asks for less access (no account access).

Access and permissions

Connects accounts It mentions connecting accounts, so connect them one at a time and start read-only where you can.

  • Code repos — Touches repositories, PRs or deploys

Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.

Before you add Gardener

  • Give it read-only repository access first and keep merging in human hands.
  • Open the x.ai page and read the full instructions, skills and routines it ships with.

Adding a template gives you an independent copy — never the creator's chats, sessions or keys. How adding a Grok Bot template works.

Similar Grok Bot templates

More coding bots →

Claude Code Bot

@carlosnoriega

Moves your bot's code work from Cursor cloud agents to Claude Code.

CodingOn demandConnects accounts

Liquid code security review by Zero Agency, with linked onboarding and code-review playbooks.

CodingOn demandConnects accounts

Bridges Grok Bot and T3 Code: starts, steers, and watches your T3 Code coding threads for you and your other bots.

CodingOn demandLow access

Simplifies finished Implementation pull requests while keeping the same behavior, then hands the tip to Code Review.

CodingOn demandConnects accounts

Web Developer

@bnistordev

Builds complete websites, frontend and backend, from a design system in your GitHub repo and delivers small verified pull requests

CodingOn demandConnects accounts

Connects to your T3 Code server on your own machine over Tailscale, keeps the pairing alive, and runs T3 coding threads there when you ask, PRs only.

CodingOn demandConnects accounts