A code change you can review

Home Workflows A code change you can review

Give a coding assistant a bounded task, inspect the proposed change, and validate behavior before integration.

Trigger and approved inputs

Begin with an isolated checkout, a clear issue, expected behavior, project instructions, and relevant tests. Supply sample data rather than production secrets. Limit the tools and network access to the work.

The steps

Keep each stage visible and preserve the evidence needed for the next one.

  1. Ask the assistant to inspect the relevant code and clarify uncertain requirements.
  2. Define a small implementation scope and the behavior to verify.
  3. Produce the change in the controlled checkout.
  4. Run the relevant checks and inspect the diff, dependencies, and security assumptions.
  5. Have a maintainer decide whether to integrate and how to release or roll back.

The human checkpoint

The maintainer reviews the actual code and evidence, including behavior that tests may miss. Passing a generated test is not enough when the test merely repeats the implementation’s assumptions.

Test before making it routine

Check the desired behavior, regressions in nearby code, invalid inputs, and relevant security boundaries. Use established project checks and add targeted validation when the change warrants it.

When the process should stop

Pause for unclear requirements, unavailable dependencies, unexpected production access, or changes outside the task. Do not let a failed check become a reason to weaken the check without understanding it.

Would an agent help?

A coding agent can inspect files, change code, and use test results as feedback. Keep the task bounded and the integration decision with a maintainer.

Sources and verification

About GitHub Copilot · GitHub

Agent sandbox security · OpenAI

Share this page