Know what matters before you open the tab
Every issue arrives labelled with severity, category, and the components it touches — so the queue sorts itself and the urgent things surface first.
Open-source issue triage
Every bug report arrives with a fix attached.
Sentifix reads each new GitHub issue, traces it back to the code that caused it, and replies with a root cause and a working patch — usually within 30 seconds of the issue being opened.
Discount codes silently ignored when cart total is exactly £50
MIT licensed — read every line
Self-host it — your code never leaves your infra
GitHub and Slack — report from either
Runs in ~30s per issue
The pipeline, end to end
Watch it work.
Seventy-two seconds: an issue classified, the repository searched, a root cause found, a patch written, and the patch scored. The diff and the score on screen are the real output of a real run.
Why teams turn it on
Your backlog stops growing faster than you can read it.
Triage is the tax on every popular repository. Sentifix pays it for you, and shows its work.
Skip the hour spent finding the right file
Sentifix indexes your repository and searches it the way a reviewer would — following stack traces and imports, not just matching words — then names the exact lines at fault.
Start from a patch, not a blank editor
You get a real unified diff you can read, argue with, or apply. Nothing is ever pushed or merged — the change stays a suggestion until a human says otherwise.
Two ways in
Not every bug report starts as a GitHub issue.
Plenty of them start as someone in a channel saying “hey, checkout is broken again”. Sentifix takes that as a report too — mention it, and the triage comes back in the thread.
Someone opens an issue. Sentifix picks it up from the webhook and replies on the thread with the diagnosis and a patch.
Best for reports that already have a stack trace or a reproduction.
priya
@sentifix discount codes aren't applying on £50 carts
Sentifix app
Root cause in
applyDiscount() — inclusive threshold compared with >. Patch and eval score attached.
Best for the reports that would otherwise never become issues at all.
How it works
Three steps, and none of them are yours.
Install once. Everything after that happens on its own, in the open, in the issue thread.
An issue is opened
Sentifix picks it up from the webhook and classifies it — what kind of bug, how severe, which parts of the system it touches.
It reads your code
It searches the indexed repository for the code the report points at, pulls in the surrounding context, and works out the root cause.
It posts a fix
A comment lands on the issue with the diagnosis and a proposed diff — already scored for correctness and safety before you ever see it.
Built to be checked
Every patch is graded before it reaches you.
An AI that guesses confidently is worse than no AI at all. So Sentifix scores its own output against the issue it was given, and that score ships with the suggestion.
“Replace this with a real quote once you have one — a maintainer describing what triage cost them before, and what it costs now.”
3
independent scores on every patch — correctness, completeness, and safety
0
commits pushed without a human approving them first
Pricing
Free if you host it. Cheap if you don't.
The whole thing is open source. Paying is for people who would rather not run a queue, a database, and a vector store themselves.
Self-hosted
£0
Run it on your own box with your own API keys.
- Unlimited repositories
- Unlimited triage runs
- Docker Compose, one command
- Community support
Team
Most teams£49 / month
Hosted, maintained, and watching your repos.
- 10 repositories
- 200 triaged issues each month
- Slack reporting and replies
- Quality scores on every patch
- Email support
Scale
Talk to us
For busy monorepos and larger organisations.
- Unlimited repositories
- Volume triage pricing
- Private deployment in your account
- Priority support
Questions
The things people ask first.
Does it push code to my repository?
No. Sentifix writes a comment containing a proposed diff. Applying it, editing it, or ignoring it is entirely your call — nothing reaches a branch until you approve it from the dashboard.
Where does my source code go?
If you self-host, nowhere — the index lives in your own database on your own infrastructure. On the hosted plan, your repository is indexed on our servers and used only to answer issues in that repository.
Which languages does it work with?
Any language in your repository can be indexed and searched. Patch quality is strongest where the codebase has clear structure and the issue includes a stack trace or a reproduction.
What if the suggested fix is wrong?
Sometimes it will be. That's why every patch is scored before posting and nothing is applied automatically. Treat a Sentifix comment as a well-prepared first draft from a reviewer who has already read the code.
Can I control which issues it responds to?
Yes. Run it on everything, restrict it to a single label, or trigger it manually by commenting /sentifix on the issues you want looked at.
What access does the Slack app need?
Three scopes: read the mentions addressed to it, and post messages. It cannot read channel history, browse other conversations, or see anything it wasn't explicitly mentioned in.
How long does setup take?
Install the GitHub App, pick your repositories, and the first index runs immediately. Most teams see their first triaged issue within a few minutes.
Point it at one noisy repository.
Free to try, no card, and you can uninstall it in two clicks if it isn't pulling its weight.
Root cause. The eligibility check in
applyDiscount()uses>where the threshold is meant to be inclusive, so a cart at exactly the minimum is rejected.✓ Patch reviewed and scored before posting · 3 related tests found