SendIt
I got tired of the same ritual every time I finished a piece of work: check what's changed, write a commit message, remember whether this repo wants a ticket number in the branch name or the commit, run the tests (or, honestly, skip that step when I was in a hurry), then push. Multiply that across a dozen repos with slightly different conventions and it's a lot of manual, error-prone repetition for something that should be routine.
SendIt turns all of that into one command: sendit.
Why I built it
- Nothing broken gets pushed. SendIt runs your project's test suite before it commits, so a rushed push can't quietly ship a failure — you find out before it's on the remote, not after.
- Consistent commits without the mental overhead. It can write the commit message for you, using whichever AI provider you've already got — a hosted API, a local model, or a CLI tool like Claude Code — so messages stay meaningful without me having to compose one every single time.
- Conventions get enforced, not just remembered. Branch prefixes and ticket references are checked automatically, so the "did I follow the naming convention this repo uses" question disappears — it's no longer on me to remember.
- One command, every repo. Whether it's a solo project or a team repo with its own
rules,
senditbehaves the same way, configured per-repo where it needs to differ.
It's a small tool, but it removes a chunk of the friction between "I've finished this" and "it's safely on the remote" — which is exactly the kind of repetitive, error-prone step I like to automate away.
For installation, full command reference, and configuration details, see the GitHub repo.
