I built ReadyCheck because Claude Code can inspect the repo, but it usually does not see the bug happen. For UI/runtime bugs, that missing context matters. The useful evidence is often: what was visible on screen what I expected what I said while reproducing it which functions ran around the symptom ReadyCheck turns that into a local session Claude Code can analyze. The unusual part: it is voice-first while you reproduce the bug. Not commands. Just observations: “this button should enable now” “that value looks stale” “the list jumped after I clicked save” How It Works: In Claude Code, type: check my app or /check my app ReadyCheck launches the app. Use the app normally and say what feels wrong. End the session by exiting your app. /analyze reads the screen, spoken observations, and runtime traces. Fix plan created. Available now: macOS + Claude Code. (More platforms and coding agents are planned.) Pricing / source: Free to try during this feedback launch. Install: claude plugin marketplace add readycheck-dev/skills claude plugin install readycheck@readycheck Official website: https://readycheck.dev/ GitHub skill repo: https://github.com/readycheck-dev/skills/ (Open Source under Apache-2.0) If the voice-first flow sounds odd, this clip shows the interaction: https://youtu.be/WTj7UkfVGZU I’m looking for practical feedback from Claude Code users: Try it on one reproducible macOS app bug and tell me whether /analyze cited the right screen, voice, and trace evidence, missed important context, or still guessed. submitted by /u/Yolo-8848
Originally posted by u/Yolo-8848 on r/ClaudeCode
You must log in or # to comment.