Explain what a dependency update actually changes

Claude Code reads a dependency bump and writes what behavior in your app could change.

A note: version jump, breaking changes that touch your code, and what to test.

1. 1

   Isolate the bump

   Make the dependency change its own diff so the note is not mixed with feature work.

2. 2

   Verify the version jump

   Check the numbers against the lockfile. Reject a note that names the wrong versions.

3. 3

   Run the test it named

   If that test does not exist, add it or run the closest one you already trust.

A dependency update is in this diff. Explain what could change in our application.

Rules:
- Name the package and the version jump from the lockfile or manifest.
- List breaking changes that our code might hit. Point at the file in this repo if we call the affected API.
- If the changelog is not in the repo, say you cannot see it instead of recalling one from memory.
- End with the smallest test that would catch a break.
- Do not apply further upgrades.

Models remember changelogs that do not match your version. Trust the repo first.

Sample case written by Hidden Logic Lab. Not affiliated with Claude Code.