service · automation · AI with a person in charge

AI automation
for your web team

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.

What I automate

QA issues, theme building and site monitoring

How

Claude Code with strict permissions and a plan a person approves before anything is touched

Result

A before-and-after report and changes you review before accepting them

Mode

Remote from Havana

// what it solves

What
it solves

Concrete problems that already came up in a real project, not a list of promises.

01

Loose QA issues

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.

02

Control over what the AI does

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.

03

From design to site

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.

04

A tool that does not exist

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.

// proof

Real
proof

206automated tests in issue-bot, all green
13merged pull requests in issue-bot
277automatic checks in claude-wp-builder
138automated tests in Boardly

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.

own project · open source

A bot that fixes issues

issue-bot takes QA issues over Telegram, agrees a plan, applies the fix with Claude Code and returns a before-and-after report.

issue-bot
issue-bot conversation on Telegram with the report of an issue
// how it works

How
it works

01 · workflow02 · limits03 · plan04 · execution05 · review
01

Your workflow

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.

  • repeated task
  • fit
  • scope
02

Limits

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.

  • strict permissions
  • sandbox
  • no network
03

A plan to approve

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.

  • plan
  • approval
  • Allow / Deny
04

Apply

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.

  • local copy
  • report
  • no commit
05

Review and test

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.

  • human review
  • 206 tests
  • open source
My team gets QA issues from everywhere: screenshots, texts, albums
On which WordPress sites? issue-bot works on local copies
Yes, local development copies
Then it fits. I explain the plan and what you review
example conversation
a denial always wins
Approve planAllowDeny
✓ plan approvedplan.md · nothing is touched without approval
example: issue-bot
figures taken from the repositories
// questions

Frequently
asked

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.

Who decides what changes?

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.

Does it fit my team’s workflow?

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.

What is it built with?

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.

// let’s talk

Got something
like this in mind?

Tell me what you sell, to whom and what has to happen. I reply within 24 h.