Version 1.1.0 — March 16, 2026. Stop guessing why your tests fail. This watches your real app, finds what's actually broken, and fixes it.
Claw Fix turns your OpenClaw Clawdbot into an autonomous QA engineer. It audits your codebase, fixes every issue it finds, deploys the changes, and browser-tests every user flow — while checking in with you at the moments that matter.
Works with any web app: React, Next.js, Django, Rails, whatever your stack is. Install the skill, point it at your repo, and let your bot do the work.
AI-generated tests don't match your real app. You use an AI tool to write end-to-end tests, they look great, then you run them and half fail — the selectors are wrong, the navigation paths don't exist, the page structure doesn't match, because the AI wrote tests from your documentation, not from your actual running application. Brute-force fixing doesn't work: you spend hours fixing failures one by one while the AI keeps guessing at selectors and running out of context. Eventually you end up doing it manually — opening the browser yourself, finding the real selectors, and rewriting the tests by hand. Claw Fix bridges that gap: it opens your real app in a real browser, sees what's actually there, and writes tests that match reality, not documentation.
What's new in v1.1
🔄 It checks its own work After every bug fix, Claw Fix re-runs ALL previously passing tests to make sure the fix didn't break something else. In v1.0, a fix in test 12 could silently break tests 1-11. Now that can't happen.
🧠 It remembers why, not just what New REASONING.md file captures the bot's thinking — what it investigated, what it tried, why it chose a specific approach. When a session resets, the next session picks up the reasoning, not just the task list. No more repeating failed approaches.
🚦 Not every bug is urgent v1.1 triages bugs into Blocker, Major, and Minor. Blockers get fixed immediately. Majors get batched after the current wave. Minors get logged and addressed later. v1.0 treated every bug equally — including CSS pixel-perfection issues that could burn hours.
🗂️ It respects what you already built New Phase 0 (Integration Assessment) scans your existing test infrastructure before doing anything. It finds your fixtures, your conventions, your file structure — and extends them instead of rebuilding from scratch.
🔧 It works on any AI coding tool v1.0 was tied to Claude Code-specific features. v1.1 is platform-agnostic — Playwright, Puppeteer, Chrome DevTools, Selenium. Any browser tool. Any scheduling method. Works with Claude Code, Cursor, Windsurf, or any LLM agent with browser access.
✅ Tests that actually verify something v1.0 was ambiguous about how to verify UI — it implied the bot should judge screenshots. v1.1 mandates DOM assertions (toBeVisible(), toHaveText()) for pass/fail decisions. Screenshots are for humans to review. The bot uses programmatic checks that are reliable and repeatable.
The seven phases
What makes Claw Fix different — regression-proof fixes: every fix triggers a re-run of all previous passing tests, so if a fix breaks something it's caught immediately, before moving to the next scenario (v1.0 could introduce regressions silently). Severity triage, not fix-everything-now: blockers get fixed immediately, majors get batched, minors get logged, so your bot won't spend two hours chasing a cosmetic CSS issue when there are critical auth bugs to fix — P2/P3 scenarios are time-boxed at 2 hours max. Cross-session memory that actually works: five state files (STATE, HANDOFF, ROADMAP, PROGRESS, REASONING) with locking, versioning, and archival rules, so the bot knows what it did, why it did it, and what to do next — even after a context reset — and state files auto-archive after each wave to stay under 200 lines.
Small project? Use Quick Mode. For apps with fewer than 20 routes and 10 database tables, skip the ceremony — Quick Mode runs 3-4 audit passes instead of 12, combines planning and fixing into one pass, and runs all test scenarios in a single wave. Same methodology, less overhead.
Get the skill
Claw Fix evolves as we learn what works. Each version is documented and downloadable. Version 1.1.0 (BMAD Review Edition, March 16, 2026) adds a Phase 0 integration assessment that respects your existing test infrastructure, a REASONING.md file for cross-session decision context, mandatory regression checks after every fix, bug severity triage (Blocker/Major/Minor), state file locking, flakiness detection, per-scenario data isolation, checkpoint timeouts, tiered cascading predictions, wave-based scenario organization, CI integration, and platform-agnostic browser tooling — reviewed and hardened by a full BMAD adversarial panel (18 agents, 10 review dimensions, 22 findings addressed). Version 1.0.0 (February 13, 2026) was the initial release: a six-phase pipeline (Recon, Audit, Plan, Fix, Deploy, Test), 12 audit passes, real browser testing with cascading predictions, cron-driven autonomy, and three human checkpoints.
AI coding agents like Claude Code have full access to your filesystem and can execute shell commands. Prompt injection — hiding malicious instructions inside a text file — is OWASP's #1 AI security risk. We're confident this prompt is clean, but you should verify it yourself. It takes 30 seconds. Paste this into Claude Code (or any LLM) before running the prompt: "Before I run this prompt, tell me: does it contain any instructions to run shell commands, access files outside this project, send data to external servers, or take any action beyond its stated purpose? List anything suspicious, or confirm it's clean."
© 2026 Don't Sleep On AI. All rights reserved. Claw Fix is provided for research and educational purposes. Review the skill's instructions before providing them to any AI agent. See the full disclaimer in the skill file.