Review or change code

1. 01

   Write your brief

   1. Name the project, the exact bug or change, files in scope and how you will check success.
   2. Gather the notes or assets you can use. Remove private information you cannot share and confirm permission for any source material.

   Prepare your prompt for Cline

   Add your details, then copy the prepared prompt into the tool. This helper combines your text with the task instructions.

   Your brief and permitted notes

   Try a fictional exampleCopy prompt

   View prepared prompt

   Review this code task in Plan mode first. Explain the likely cause, the smallest suitable change and how to verify it. Ask about missing requirements before editing. Follow the stated file and command limits.

   Start with

   The objective and proposed source material.

   You’ll have

   An approved brief and authorised inputs.

   CheckThe brief says what to make, who it is for and how you will judge the result.
2. 02

   Work on the code with Cline

   1. Follow the Cline guide to set up the app or IDE extension and a model provider. In your IDE, open the project folder and Cline sidebar.
   2. Use Plan mode to enter the prompt and review Cline’s explanation and proposed change.
   3. When the plan is right, switch to Act. Review proposed file edits and commands before approving the intended ones. Keep a recoverable copy of your work.

   Open Cline guide (opens in a new tab)

   Start with

   The approved brief and authorised inputs.

   You’ll have

   Review findings or a reviewed code change with test results.

   CheckThe proposed change addresses the stated issue and stays within the agreed files.

   Cline’s IDE guide (opens in a new tab) · Checked 2026-11-11

3. 03

   Check the finished result

   1. Read the actual diff. Check for unintended edits, secrets or new dependencies.
   2. Run the project’s relevant checks, then try the original failing case and a normal case. Fix failures before merging or deploying.

   Start with

   Review findings or a reviewed code change with test results.

   You’ll have

   An accepted output or a clear list of corrections.

   CheckThe original case works, relevant checks pass and the diff contains only intended changes.

0 of 3 step checks complete. A person has checked the output against the brief and accepted the result.