Regression Detection Prompt
Asking for a fix that preserves the intended improvement prevents the common cycle of fixing one thing while breaking another.
I recently updated my {{prompt_name}} prompt and I'm seeing unexpected behavior.\n\nPrevious version (was working well):\n{{previous_version}}\n\nCurrent version:\n{{current_version}}\n\nObserved regression:\n{{regression_description}}\n\nAnalyze:\n1. Which specific changes likely caused the regression\n2. Why the change had this unintended effect\n3. A fix that addresses the regression without losing the intended improvement\n4. Test cases I should run to verify the fix\n5. Guidelines for future edits to this prompt to avoid similar regressions
Variables to customize
Why this prompt works
Asking for a fix that preserves the intended improvement prevents the common cycle of fixing one thing while breaking another.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Forcing the agent to plan before acting prevents premature execution and wasted steps. Explicit dependency mapping enables parallel execution and catches logical gaps early.
Tool Selection AgentThe ReAct pattern (Reason + Act) creates an explicit reasoning trace that improves tool selection accuracy. The error-handling rule prevents infinite retry loops.
Prompt CompressorExplicitly requiring all functional requirements to be preserved prevents the model from over-compressing and losing critical instructions.
Memory Management AgentExplicit memory read/write instructions create agents that improve over time. Categorization keeps memories organized, and the deduplication rule prevents context bloat.