I love it. I’m producing so much that I often forget what to test. I want a really quick tl;dr on what changed, and what I should test. In fact, I want this streamed to a file, called my QA-log.md. At the end of every week, I can ask claude or some other tool to summarize this qa-log.md and produce a changelog when I do a major release.
How am I doing this today? I use v0’s custom instructions. I added one that is always enabled with this promptlet:
After each change, summarize with QA instructions in bold
After each change, summarize with QA instructions in bold
---
## QA INSTRUCTIONS
_date-time of change_
**What changed**: bulleted list of things that changed
**Check this**: bulleted list of check that when you open XYZ experience, behavior XYZ is observed
---
That’s a solid workflow. I’d probably make the custom instruction a little stricter so v0 keeps the summary short and testable instead of turning it into a long recap.
Something like this may work better:
After every meaningful code change, append a short QA summary.
Format exactly like this:
## QA INSTRUCTIONS
Date/time: <current date/time if available>
**What changed**
- 1–3 bullets only
**Check this**
- 1–3 specific manual checks
- Include the page/route/component to test
- Include the expected result
Keep it concise. Do not include implementation details unless they affect QA.
For the QA-log.md part, I’d ask v0 to create and maintain that file explicitly:
Create a `QA-log.md` file. After each meaningful change, append the QA summary to that file instead of only writing it in chat. Keep the newest entry at the top.
I’d still keep the chat summary too, because it helps while you’re actively iterating, but having the file gives you a clean artifact to summarize into release notes later.
