A small cleanup becomes risky when long-lived workspaces each carry their own history.
The practical check
Record the shared files, local exceptions, and verification steps before changing several environments.
Where AI fits
AI can compare environment inventories and flag files whose local state diverges from the intended baseline.
The human decision
People approve migrations and verify the state of each environment.
The lesson
A migration is repeatable when its state and verification record travel with the change.
Shared files, local exceptions, and the environment inventory are the migration record traced in the Build Log companion.
AI Skills
Use this lesson with the AI assistant you already use
Use this to prepare a reviewable next step without changing any system.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI agent
LESSON: Prepare an environment migration record
WHAT TO SHARE:
A de-identified description of the work, current evidence, and the decision you are considering.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. Record the shared files, local exceptions, and verification steps before changing several environments.
3. Identify the narrowest useful next review step.
RETURN:
A short table with the evidence, uncertainty, human-owned decision, and next action.
BOUNDARY: Do not change records, contact anyone, route work, publish content, or act in an external system. A person must review the evidence and approve every consequential step.
