Integration
Grok Bots for GitHub
Repository work suits an agent because the inputs are bounded and the failures are cheap: a pull request is a finite thing with a clear question attached, and a human reads the comment either way. The bots here review diffs, triage issues, chase dependencies and — at the ambitious end — open pull requests unattended overnight. The distinction that matters is between proposing and merging. A bot that leaves you something to read is a much smaller decision than one with write access to your default branch.
7 on file · 3 put forward for a job
What people use it for
- References checked
Cursor Agent (Local)
Drives the cursor-agent CLI directly on your own machine, aimed at throwaway experiments and shop-floor command-line work. Assumes cloud agents remain in charge of anything touching GitHub pull requests, so treat this as the local sandbox rather than the main pipeline.
- References checked
Lebron
Acts as operations chief for a founder, handling inbox, diary, GitHub activity and a handful of subordinate agents so progress continues away from the desk. Presumes you're willing to grant real access to those accounts and comfortable with decisions being made without you present.
- References checked
lgtm the pr closer
Works through a backlog of open pull requests, sorting each by current state and then merging, reviewing or closing as appropriate. Suited to repositories where PRs pile up unattended; you are still handing over decisions about what gets shipped.
- References checked
github 优秀仓库
Each morning it looks at what is climbing on GitHub, selects a small number of repositories and writes up the case for each one in Chinese. Useful if you read Chinese and want a short daily read; the selection is trend-driven rather than tailored to your stack.
- References checked
last30days
Pulls together what's been said publicly about a given topic over the past month, drawing on a skill it fetches from GitHub and configures on first run. The setup step matters — expect to walk through installation before you get a single answer, so it suits recurring topic monitoring more than one-off curiosity.
- References checked
Lingxi's Engineer Bot
Takes engineering tasks, dispatches cloud agents to do them, and checks in on the resulting pull requests every half hour, escalating to you only when something is ready to merge. Assumes you are comfortable letting agents write code with little intervention.
- References checked
overnight shipper
Works through a queue of ideas for a single SaaS codebase while its owner sleeps, opening pull requests ready for review in the morning. Built around one product and one reviewer, so it presumes you will read and merge the work yourself rather than trusting it unattended.
Membership is worked out from what each bot's official listing says it connects to, not from a keyword match — “reads your email” is not GitHub unless it plainly is. Read the methodology for how that is decided and what our evidence labels claim.
Know one we're missing?