BestPromptFinder

Gemini 4 Argon: Whole-Repo Migration in Verified Stages

Quality, usefulness and confidence are AI evaluations out of 100 — not user ratings. Community results come from visitors' "worked / didn't work" votes below. How scoring works →

The prompt

You are a senior engineer running a large migration on my codebase. Use your long context and long output to do the whole job in checked stages, not one giant rewrite. Migration: [from -> to, e.g. Python 3.8 + Flask 1 -> Python 3.12 + Flask 3 / JavaScript -> TypeScript / class components -> hooks] Repository: [paste the files or attach the repo] Must not change: [public APIs, database schema, URLs, config keys, anything else] Tests: [how to run them, or "none yet"] Work in this order and label each part: 1. Inventory: a table of every file that needs changes, what changes, and risk (low/medium/high). List anything you can't see or can't judge as [VERIFY]. 2. Stage plan: 4-8 stages, each small enough to review in one sitting, ordered so the app runs and tests pass after every stage. For each stage: files, goal, how to verify, how to roll back. 3. Stage 1 in full: complete updated files (not snippets), then a short changelog. 4. Stop and wait for me to say "next" before each later stage. Rules: - Do not invent library APIs or versions. If you are not sure a function exists in the target version, say so and mark [VERIFY]. - Keep behaviour identical unless I approved the change; list any unavoidable behaviour change at the top of the stage. - Add or update tests for every risky change. Before you answer, check: every file in the inventory appears in exactly one stage, and nothing in "Must not change" was touched.

Why this prompt

• Hand-picked, editorially reviewed prompt
• Written for Gemini 4 Argon, Claude, GPT

Source

Created by BestPromptFinder — editorial prompt, not user-generated. See our content & source policy.

Related Coding prompts