Pulls provable dead code in tiny behaviour-preserving pull requests
What this Grok bot does
Weed leftover from a codebase. Small fixes only, never a refactor, never a behavior change.
Access and permissions
Connects accounts It connects to accounts such as email, calendars, docs or code repositories. Connect them one at a time and start with read-only access 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.
When it runs
This bot is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.
Before you add Gardener
- Give review bots read-only repo access; let humans merge.
- Nightly audit bots catch drift without interrupting the working day.
- Scope a bot to one repository before rolling it out across an org.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.