personal project · open source

A bot that
fixes QA issues

issue-bot takes QA issues for a local WordPress site over Telegram, agrees a fix plan in chat, applies the fix with Claude Code and sends back a before and after report. I wrote all of it.

github.com/Lacho00/issue-bot
issue-bot: Telegram bot that fixes QA issues with Claude Code
206automated tests
13merged pull requests
MITopen source
What it is

A Telegram bot that takes a QA issue all the way to a report

My role

Idea, design, code, tests and deployment, on my own

Status

In daily use on my local WordPress sites

License

MIT, the code is on GitHub

// the bot, step by step

A face
for every step

The mascot is a robot with a bug on its antenna. Its expression follows the path of an issue, and the report draws the happy, worried or neutral one depending on the state of the issues.

issue-bot mascot thinking, with bubbles above its head
01 · detectsThinking
issue-bot mascot with a neutral face
02 · plansNeutral
issue-bot mascot with narrowed eyes, working
03 · fixesWorking
issue-bot mascot smiling, with the issue fixed
04 · reportsHappy
issue-bot mascot looking worried, with an issue still pending
if something is leftWorried
// the problem

From QA
to report

A QA team sends loose issues: screenshots, forwarded text, albums. Someone has to work out which site they mean, open the code, propose a fix, apply it and prove it worked.

issue-bot walks that path with a person in charge. You forward the messages, approve the plan and get a report with the QA screenshot next to Claude’s.

01

Detects the site

It pulls host names from the URLs in the message and looks them up in each .wp-create.json and in the Apache vhosts. One match opens the job; several or none show buttons to choose.

02

Agrees a plan

It collects the messages into a batch that closes after 2 minutes or with /plan. Claude reads the site, proposes a plan and changes nothing until you press Approve plan.

03

Fixes with Claude Code

It runs Claude Code headless under a strict permission policy. No commit and no push: changes stay in the working tree for you to review.

04

Reports before and after

It renders an HTML with status KPIs and a card per issue, the QA screenshot next to Claude’s. Anything you type afterwards is a correction and starts another round.

// security

Control
before speed

The bot runs Claude Code against your sites’ files, driven by Telegram messages. I treated it as remote access to that machine.

// what the hook decides
  • git commitdenied
  • git pushdenied
  • delete from the databasedenied
  • change .claudedenied
  • write to the sitesandbox
  • network from Bashno network
  • write in the plan phasenone
One owner onlyit ignores every other user and every other chat; the first message registers the owner
A hook before every toola PreToolUse hook denies git commit, push, database drops and edits under .claude before any allow rule
Bash in a sandboxbwrap with no network, writing only to the site and the job folder; during the plan phase, to neither
Ask when unsureanything no list covers comes with Allow and Deny buttons, and a denial always wins
Not for productionmeant for local development copies, not for live sites
// by the numbers

Project
in numbers

206automated tests, all passing
13merged pull requests
2,829lines of JavaScript in 22 modules
MITopen license, the full code is on GitHub

issue-bot is a personal tool, not client work: there are no business results to report. The numbers come from the repository.

Node.js 22grammYClaude CodeTelegram Bot APIMCP SDKZodPlaywrightWP-CLIsystemdGitHub Actions
// your project

Got a project in mind?

Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.