Coding Tools

Claude Code

Inspect and revise a small repository task with Claude Code, then match the proposed tests to the acceptance criteria.

Review checked

Example tasks

  • Finding the files relevant to a small code change
  • Reviewing a proposed test plan before editing
  • Rechecking test coverage when an acceptance criterion changes

Check before use

  • A proposed test plan can miss an important branch or check the wrong result
  • Check command permissions and review dependency, license, and file changes before accepting a patch
  • A local terminal session is not the same as offline processing; check the applicable data policy before sharing private code

Check the Plan Before Changing Code

Anthropic’s Claude Code overview describes inspecting code, making edits, and running commands. Start with a fictional request form and keep the first pass read-only. If the requirements say saving a draft must not submit it, check that the test plan would catch a change that makes those actions behave the same way. The acceptance criteria practice pack lets you compare a proposed plan with its original requirements.

Recheck Coverage When Requirements Change

Keep the requirement and its test together. When a rule changes, update the relevant test and review the actual diff before accepting edits. Use demo data for trials. Before connecting private code, review Anthropic’s permissions guide, pricing and cost guidance, data usage, and privacy policy.

More use cases and potential advantages

Ways to explore

  • Review a fictional draft form's acceptance criteria before any edits
  • Identify where the plan tests saving a draft separately from submitting it
  • Review the eventual diff and check that each changed criterion still has a test

Potential advantages

  • Anthropic documents reading project files, editing, and running commands
  • Walking through requirements before an edit makes missed cases easier to spot