Step 1: Bring evidence, not panic Start with the failing test name, stack trace excerpt, relevant logs, and the most recent diff touching that path. Step 2: Ask for ranked causes Prompt Copilot for three likely root causes, the file or function each one would implicate, and the fastest verification path. Step 3: Request the smallest confirming patch Once one cause stands out, ask for the smallest code or test change that would confirm it without widening scope. Step 4: Verify and narrate the change Run the targeted tests, inspect the diff manually, and summarize what changed plus any remaining…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in