TechnicalCollectible prompt
Check an AI tool's changes before you accept them
Act as a careful senior reviewer. My AI tool changed my {{tech_stack}} project for this task: {{page_or_feature}}. Here is the diff, from git or the tool's change view:
{{code}}
This isn't a general code review. Judge whether this diff does what was asked, and only that.
1. Summarize the change in three plain sentences, then list every file touched and whether the task needed it.
2. Flag scope creep: renamed variables, reformatted files, rewritten components, moved code, or improvements nobody asked for. They hide real changes and cause regressions.
3. Flag silent removals: deleted conditions, error handling, validation, analytics calls, accessibility attributes or whole functions. For each, say whether anything depended on it.
4. Check the tests: were any deleted, skipped, loosened, or changed to match new, wrong behavior? Was a test added for the new behavior?
5. Check for quiet security and data changes: weakened access rules or policies, secrets in browser code, ts-ignore or any types, disabled lint rules, new packages (and whether they're real and maintained), migrations, and edits to environment or config files.
6. Check for invented APIs: imports, functions or options that don't exist in the versions this project uses.
Verdict: accept, accept with these fixes, or reject and retry. For anything to undo, name the exact files or hunks to revert and write a tighter prompt for the retry. Then list what I should click through to confirm it works.
Technicalnvoka.com/library/nvoka-check-an-ai-tools-changes-before-you-accept-themScan to open
Technical
Check an AI tool's changes before you accept them
Read an AI-made diff for scope creep, deleted logic, weakened tests and quiet security changes.
Curated by Nvoka
Claude CodeCursorGitHub CopilotCodex
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 3 filledYour prompt
Act as a careful senior reviewer. My AI tool changed my {{tech_stack}} project for this task: {{page_or_feature}}. Here is the diff, from git or the tool's change view:
{{code}}
This isn't a general code review. Judge whether this diff does what was asked, and only that.
1. Summarize the change in three plain sentences, then list every file touched and whether the task needed it.
2. Flag scope creep: renamed variables, reformatted files, rewritten components, moved code, or improvements nobody asked for. They hide real changes and cause regressions.
3. Flag silent removals: deleted conditions, error handling, validation, analytics calls, accessibility attributes or whole functions. For each, say whether anything depended on it.
4. Check the tests: were any deleted, skipped, loosened, or changed to match new, wrong behavior? Was a test added for the new behavior?
5. Check for quiet security and data changes: weakened access rules or policies, secrets in browser code, ts-ignore or any types, disabled lint rules, new packages (and whether they're real and maintained), migrations, and edits to environment or config files.
6. Check for invented APIs: imports, functions or options that don't exist in the versions this project uses.
Verdict: accept, accept with these fixes, or reject and retry. For anything to undo, name the exact files or hunks to revert and write a tighter prompt for the retry. Then list what I should click through to confirm it works.