The outcome

Produce a focused improvement that survives review and execution.

Step by step

A workflow you can repeat.

  1. 01

    Provide the smallest complete code sample plus its language, runtime, expected behavior, and failure.

  2. 02

    Ask for diagnosis before requesting rewritten code.

  3. 03

    Require the response to distinguish correctness bugs, security risks, performance concerns, and style preferences.

  4. 04

    Apply one change at a time and compare the new behavior with the original acceptance criteria.

  5. 05

    Run tests, static analysis, and a manual review in the real project before accepting the suggestion.

Working standard

What good use looks like.

  • Never paste secrets.
  • Keep project context authoritative.
  • Reject rewrites that change behavior without explanation.

Official references

Check the current product documentation.