Meet shovel.bot
shovel.bot watches your software delivery lifecycle around the clock — so you find out about problems before your customers do.
It connects pull requests, code reviews, CI/CD runs, server health, and incident history into one place, so when something breaks, the context is already there — no digging through Slack threads, GitHub, and dashboards to piece together what happened.
What shovel.bot does today
shovel.bot is the primary interface — a multi-tenant Slack bot your team interacts with via /shovel slash commands, direct messages, or @mentions in any channel.
PR Management
List open pull requests, inspect PR details, and merge by squash — all without leaving Slack. Set a default repo once so you never have to type it again. shovel.bot tracks every PR through its lifecycle and reminds your team when reviews are overdue.
AI Code Review
Ask shovel.bot to review any PR and it will analyze the diff via GitHub Models, post the review directly to GitHub, and drop a link in your Slack channel — in seconds.
Operational Signals
shovel.watch runs continuously on your servers — monitoring endpoint health, scanning logs for errors, tracking system metrics, and verifying backups. Those signals flow through shovel.bot into Slack.
Context, without the digging
When something breaks in production, engineers spend the first 20 minutes just assembling context — digging through Slack threads, GitHub PRs, CI logs, and monitoring dashboards. shovel.bot is being built to fix that.
It already knows the state of your repos, your pipelines, and your servers, so you ask a question in Slack and get an answer — not a pile of tabs to sort through. Less digging, faster answers, more time back in your day.
Rather than firing off a bare alert that something is wrong, shovel.bot synthesizes what it knows — the recent deploy, the PR behind it, the error pattern in the logs — into a plain-language explanation of the problem, delivered right in Slack.