Next up
Your to-dos, its GitHub issues and milestones, and the TODOs in its code, ranked. Do this opens a conversation in a copy on its own branch, prompt waiting.
🗂️ Runs your dev day
Every repo. Every server. Every hour.
The repos you work in, their dev servers, what needs you, what to do next and how long it all took. Plus routines and workflows that start the work themselves.
Projects
What needs you, across every repo.
Projects lists the repos he's seen you work in, plus any you add. Each row says in a few words what he already knows: failing CI, vulnerable packages, commits no remote has, tests that flaked, hours this week.
One inbox
Pull requests waiting on your review, new comments on yours, stale branches and copies left behind, across every repo.
GitLab too
Merge requests join the inbox, his CI sign and the project's Health card.
A page per project
Next up, Pulse, Health, Releases, Helpers and your recent conversations in it.
Dev servers
When it falls over, he holds up a sign.
Start runs a dev script with the project's own package manager, and a :5173 pill sits by the crab. When one crashes he raises a red sign and the card marks the error lines. Nothing is sent to Claude until you say so.
A port that's taken
"Port 3000 was already taken, by node.exe." Use :3001 instead, or Stop node.exe after asking.
Before you start
A note says what the project needs that this PC hasn't got, like settings in
.env.examplenone of your.envfiles set.Servers keep running
They're picked back up, log and all, when Shellby starts again. Or choose to stop them on quit.
Start from where the work is
What should I do next?
Fix this build
Hands Claude the failing step's log from a red pull request, trimmed, capped and with secrets blanked out.
Address the review
Quotes the review comments still open, so Claude starts from what reviewers asked for.
Errors from Sentry
New production errors, each with Fix this error: a copy and a conversation with the stack trace.
When did this break?
Say what broke and pick the last version that worked. Claude bisects it.
Show me around
A tour of any repo: install, run, test, the map of its folders and one real path through the code.
Check the docs
Claude checks the README and docs against the code and reports what's out of date. It changes nothing.
Linear and Jira
Issues from your tracker, with Do this on each, on a branch named for it.
Open a draft pull request
Push the copy's branch and open a draft that closes the issue.
Time on each project
Timesheets that fill themselves in.
He works out how long you spend on each project from what he already sees, for timesheets and invoices. Off until you turn it on.
Clients and rates
A client and an hourly rate per project, billable or not, rounded the way you invoice.
Timesheets
Save PDF for a client, Save CSV for your invoicing tool, or Copy as text.
Send to your time tracker
A day at a time to Toggl Track, Clockify or Harvest.
Private
Everything stays on this PC and is never synced, except the days you send.
Keeping it healthy
Flaky tests, old packages, unpushed work.
Flaky tests, spotted
A test that fails then passes with the code unchanged. Twice in a week and he says so. Reads Jest, Vitest, pytest, Go, Rust, Playwright and more.
Fix it for real
Claude finds the cause (timing, shared state, order, clock) and fixes that rather than adding retries, then runs it 20 times.
Dependency watch
Weekly outdated and vulnerability checks. Bump & open a PR bumps what's safe, runs the tests and opens the pull request.
Is it safe to leave?
Checks for unpushed commits, uncommitted changes, stashes and anything that looks like a secret before you lock up.
Shutdowns wait
A shutdown with unpushed work or Claude mid-task is held up with the reason.
Streaks and nudges
A streak for consecutive days, and a nudge when a repo goes quiet: "You haven't committed to 3d-rack in 5 days 🐚".
Routines and workflows
Work that starts itself.
A schedule, a red build, a release, a file landing in a folder or Claude Code asking starts a list of steps: Claude, PowerShell commands, web requests, files, a question for you, a message to your phone.
Run it when my limit resets
Queue heavy tasks and they start when your window resets, overnight too, with the PC kept awake. A task that runs out partway carries on after the next reset.
Routines
One task on a schedule, like "every Friday at 5, tidy Downloads". Missed runs catch up when your PC wakes.
Build it with Claude
Describe it in a sentence; Claude lays it out on the map. Fix with Claude repairs a failed run.
Your MCP servers in steps
Tick the servers a step may use and Claude files the Linear issue or posts to Slack without stopping to ask.
Secrets
API keys stay in Secrets, encrypted by Windows, and are never allowed in a prompt.
Spending guard
Routines and workflows stop before they use the share of your window you keep for yourself (25% unless you change it).
Pair it with n8n
Web hooks in, anything out.
A script or service can start a workflow with a web hook, and a workflow can call any web request. Pair it with n8n for everything Shellby doesn't do itself.
$ shellby do "tidy my Downloads" $ shellby do @review $ shellby time last-week $ shellby status
Next
🌊 Gets out more
Get Shellby. It's free.
Free for Windows 10 and 11. Bring your Claude Pro or Max plan, or just keep him for company.