Gardener
Pulls provable dead code in tiny behaviour-preserving pull requests
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
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.
Description as published on the x.ai share page when last checked (2026-11-01).
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
An engineering team, especially one merging lots of AI-written code, that wants small cleanup pull requests removing provably dead code.
Not for
Anyone wanting refactors, style fixes, or architecture changes, all of which it avoids.
What it does
It hunts recent merges and spike leftovers for removable cruft: code with no callers, duplicate writes, flags already shipped, misleading comments, and unreferenced files. Each pull request names the leftover in one sentence, and it keeps only one open at a time. If a change would be noticeable to someone using the product, it asks one question and stops.
First messages to try
- Look at merges from the last two weeks and find one provable weed.
- Is the old checkout flag safe to remove? It's been on in production since July.
- My last gardener PR is merged. Go find the next one.
Apps and accounts
Its description mentions opening pull requests on a codebase but does not name a specific code host or service.
Cautions
- It opens pull requests on your repository, so it needs write access there.
- With one PR at a time, it waits if you leave the last one unmerged.
- Review each removal, since code that looks unused to the Bot may still be reached dynamically.
Compare with: PR Reviewer by MustafaHackBot9000 by Mark MarshallAutomation Bot by Ezra Black
Before you add it
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Tyler Klose. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/gardener)
Or promote this template in the labelled Featured row, from $19.