Does the AI touch production?
No. issue-bot is built for local development copies, not for production sites. It makes no commit and no push: changes stay in the working tree for you to review.
I automate repeated tasks of a web team with AI and a person in charge: a bot that takes QA issues over Telegram and applies the fix, and a flow that turns an approved design into a WordPress theme. They are tools I use every day, with tests and open source.
QA issues, theme building and site monitoring
Claude Code with strict permissions and a plan a person approves before anything is touched
A before-and-after report and changes you review before accepting them
Remote from Havana
Concrete problems that already came up in a real project, not a list of promises.
Screenshots, forwarded texts and albums. issue-bot finds the site from the URLs, agrees a plan in chat, applies the fix and returns a report with the QA screenshot next to Claude’s.
A hook denies git commit, git push, database deletes and changes to .claude. Bash runs in a sandbox with no network, and a denial always wins.
claude-wp-builder takes an approved design to a bilingual, editable WordPress theme in five steps, and audits it with 277 automatic checks before delivery.
When none covers the flow I write my own. Boardly gathers five checks per site in a dashboard built with Next.js 16, with 138 automated tests.
issue-bot and Boardly are projects of my own, not client work: there are no business results to report and the figures come from the repositories. claude-wp-builder is co-authored with Yojahny Chavez.
You tell me which task your web team keeps repeating. We check whether it fits before quoting; if your workflow is a different one, I say so, because I have no case here with another kind of team.
Before giving the AI any work I fix what it cannot do: no commit or push, no database deletes, no touching .claude. Bash runs in a sandbox with no network.
The AI proposes a plan in chat and touches nothing until you press Approve plan. Anything doubtful comes with Allow and Deny buttons, and a denial always wins.
With the plan approved, Claude Code applies the fix on the local copy and returns a report with the QA screenshot next to Claude’s. You review the changes.
The changes stay in the working tree until you accept them. The tools come with automatic tests: 206 in issue-bot and 277 checks in claude-wp-builder.
No. issue-bot is built for local development copies, not for production sites. It makes no commit and no push: changes stay in the working tree for you to review.
A person. Claude proposes a plan and touches nothing until you press Approve plan. Anything doubtful comes up with Allow and Deny buttons, and a denial always wins.
issue-bot takes issues over Telegram and works on local WordPress sites. If your workflow is different, we look at it when we talk about scope; there is no case here with another kind of team.
Claude Code run headless under strict permissions. The bot is Node.js 22 with grammY, and the code is on GitHub under the MIT license.
Tell me what you sell, to whom and what has to happen. I reply within 24 h.