Dependencies, diffs and reproducible handover

Learning outcome: Review what the change brings into the project.

Generated code can introduce new packages, configuration changes or assumptions about runtime versions. Inspect those additions rather than treating installation success as a complete review. Check whether the package is necessary, its source is the intended one and the project records a reproducible dependency set.

A handover should identify changed behaviour, build instructions and checks performed. Preserve required deployment files. Compare the final diff with the original task so unrelated edits are visible. Do not include local credentials, dependency folders or temporary personal test files in a source archive. A successful local preview alone does not prove that a clean environment can build it.

Worked example

A fictional feature adds a date-formatting package to display one ISO date. A reviewer notices the project already has a tested formatter. Reusing it avoids another dependency. The final handover includes the source edit, its test and the unchanged lockfile, plus the command used to build the site.

Try it yourself

Create a handover checklist for a small website fix. Include source completeness, dependency changes, build command, test evidence and a limitation statement.

You can do this exercise on paper. If using an assistant, keep to the fictional material and an approved tool.

Check your understanding

What does a successful local preview establish?

1. That all dependencies are safe and necessary
2. That the observed preview worked in that environment
3. That every clean deployment will succeed

Workbook

Download the course workbook to record your answer and compare it after the knowledge check.

Further reading

• Anthropic: effective agent design
• Anthropic: evaluating agents