Lesson 6 of 12

Structured learning draft

Verification with Code review

In GitHub Copilot for Developers, the way a learner handles verification shapes how Code review is used and evaluated. Verification checks generated claims against independent evidence. This intermediate lesson focuses on a decision or output that another person can inspect.

Learning objectives

Explain verification in the context of GitHub Copilot for Developers.
Apply Code review to a bounded practical task.
Evaluate the result using explicit quality criteria.

Instructional figureDecision matrix

Verification: from context to evidence

Verification connects bounded input to a reviewed output in GitHub Copilot for Developers.

Bounded input

Define the purpose, intended user and Code review constraints.

frames

Verification

Trace consequential claims to primary sources or reproducible calculations.

produces evidence for

Reviewed output

Compare the observed result with a normal case, boundary case and stated limitation.

Takeaway: Verification is credible only when the result can be traced back to its purpose, inputs and constraints. Verification is the decision layer between the starting context and evidence that the result is fit for purpose.

Verification checks generated claims against independent evidence. For Code review, distinguish performing an operation from demonstrating that it suits the stated purpose. Trace consequential claims to primary sources or reproducible calculations. Record assumptions that could change the conclusion.

Apply verification deliberately

State the GitHub Copilot for Developers task and the decision it supports.
Prepare a small Code review case with a known input and difficult boundary.
Trace consequential claims to primary sources or reproducible calculations.
Compare the observed result with the expected behaviour and explain differences.
Save the evidence, limitation and next action in a review record.

verification evidence record
Review point	Evidence
Purpose	The specific Code review outcome and intended user
Method	The verification decision, input and version or context
Result	Observed output plus a checked boundary case
Limitation	What the result does not establish and the next safe action

Common mistakes

Using Code review before defining what verification must achieve.
Checking only the easiest GitHub Copilot for Developers example.
Reporting a result without its input, assumptions or limitation.

Practice activity

Apply the lesson

For GitHub Copilot for Developers, complete a bounded Code review task demonstrating verification. Keep the original input, numbered method, normal test, boundary test, observed results and a 100-word self-review naming one limitation and next improvement.

Check your understanding

In GitHub Copilot for Developers, which evidence best supports a verification result produced with Code review?

A polished Code review output without its input The input, expected behaviour, normal and boundary results, and a limitation A screenshot showing the tool opened A claim that the method always works

Lesson summary

For GitHub Copilot for Developers, verification means: Verification checks generated claims against independent evidence.
A credible Code review result includes a checked boundary, not only a successful example.
The next lesson builds on this verification evidence record.

Sources and further reading

AI Risk Management Framework 1.0NIST - accessed 2026-08-21
AI PrinciplesOECD - accessed 2026-08-21

Personal study note

Your notes

Saved on this device

Notes for this lesson

0 / 12,000No saved note yet.