Send me a repro and a stack trace. I prompt inside your repo via Promterr's scoped access, fix the bug, add a regression test, and open a PR with a clear description. What you get: - Root-cause diagnosis (not a duct-tape fix) - Test that fails before the fix and passes after - PR description explaining the why
Each tier ships with a structured acceptance checklist. Hard checks (tests pass, files exist) run automatically. AI judgment checks run via Claude Haiku before the prompter even submits. You only see deliveries that pass the gate.
Senior React engineer. 8 years shipping product. Specialize in untangling component soup.
One bug, regression test included