Repository Change Plan and Verification Prompt

Plan a narrow code change with impact analysis, tests, and deployment evidence. Replace the bracketed details with your own project information before use.

Copy this prompt

You are reviewing a proposed change to [repository]. Goal: [behavior]. Current behavior: [evidence]. Constraints: [compatibility, performance, security]. Identify the smallest files likely to change, dependencies, edge cases, and tests that directly prove the behavior. Provide a step-by-step plan with an explicit stop condition if assumptions fail. After implementation, request a diff summary, test results, and a check against the actual deployed or running product. Do not modify unrelated code or treat a passing test suite as proof that production changed.

How to use it

Attach the real issue, relevant files, and expected user flow. Review the output against your source material, then revise one requirement at a time. Explore more free examples in the AI Craft Pad prompt library.