Evaluate an AI coding tool on one real change.

STEP 01Choose a bounded change

Use a repository you are authorized to access. Pick a small bug fix or feature with a clear expected outcome. Start from a clean branch so the generated work is easy to review and undo.

Confirm what repository content the selected tool can access and how its current data settings work. Do not paste credentials or private data into prompts.

STEP 02Supply the relevant context

Describe the observed behavior, expected behavior, reproduction steps, and constraints. Point to relevant files or documentation rather than asking the tool to guess the architecture.

Ask it to inspect existing conventions before editing. Record assumptions that need confirmation.

STEP 03Review proposed actions

Inspect commands and changes before approving consequential actions. Keep the first change small enough to understand. An explanation that sounds convincing does not establish correctness.

Look for unnecessary dependencies, broadened scope, changed permissions, and hidden configuration edits.

STEP 04Verify behavior

Run checks appropriate to the change. A bug fix needs evidence that the original failure is resolved and relevant neighboring behavior still works. Avoid tests that merely repeat the generated implementation.

Read the final diff yourself. Check failure handling, input validation, and whether the change follows the repository’s existing patterns.

STEP 05Compare the complete effort

Record time spent providing context, reviewing work, correcting errors, and validating the result. Compare this with your normal approach to a similar task.

The expected outcome is a reviewed change and a practical assessment of one workflow. This guide is not a benchmark or a claim about comparative coding performance.

A brief to adapt

Use this as a starting structure and replace the details with your task. It is not a guarantee of any tool’s output.

Inspect the relevant code and existing conventions first.
Problem: [observed behavior and reproduction steps]
Expected behavior: [specific outcome]
Constraints: [scope and compatibility]
Make a focused change and explain how to verify it.

Explore the tools and their sources

Cursor profile · Official product information ↗

GitHub Copilot profile · Official product information ↗

Claude Code profile · Official product information ↗

Linked product sources were checked for identity and broad positioning on 2026-11-05. The steps above are original editorial advice, not vendor-specific documentation.