testing · PromptZap Team

Regression Risk Scanner

Pre-merge ritual: traces callers, shared state, and test coverage of your diff, then gives a reasoned Low/Medium/High regression risk rating.

Framework

standard

Model targets

claude, chatgpt, gemini

Prompt text

I'm about to ship this change: [paste diff/PR description]. Before merging, tell me what could regress.

Trace through:
1. What other code paths call the functions/components being changed (search the codebase if you have access, otherwise ask me to paste the callers)
2. What shared state, config, or types this touches that other features also depend on
3. Which existing tests actually exercise this code, and whether they'd catch a regression here
4. What manual test I should run before merging that automated tests won't cover

Give me a short risk rating (Low/Medium/High) with reasoning, not just a list.