Claude Code usage tips

Reproducible practice

Build an evidence packet for one small coding task

Replace 'done' claims with a baseline, bounded request, targeted proof, broad gate, and reviewed diff.

Prerequisites

• A trusted repository and a small task with one observable outcome.
• Known test, build, lint, or manual QA commands.
• A clean baseline or an explicit list of pre-existing changes.

Steps

1. Capture the baseline

   Record current changes and the failing or missing behavior before implementation.

   git status --short
   git diff --check

2. State one acceptance check

   Give Claude the exact file scope, prohibited areas, and command or browser path that proves success.

3. Verify in layers

   Run the smallest relevant check first, then the repository gate; retain command output rather than a prose assertion.

4. Review the final evidence

   Compare status, diff, and tests, then ask an independent reviewer to challenge the result.

   git status --short
   git diff --check
   git diff --stat

Expected result

A reviewer can trace the requested outcome to a bounded diff and concrete verification output without trusting the implementer's summary.

Validation

• The acceptance check fails or is absent at baseline and passes after the change.
• No unrelated file appears in the final diff.
• A second method checks high-risk behavior or attempts to refute the conclusion.

Failure handling

Cleanup or rollback

• Revert only the bounded task changes after reviewing the patch.
• Keep failure evidence long enough to reproduce the original issue, then follow project retention rules.

Boundaries and when not to use it

• More context is not always better; give the smallest relevant files, constraints, and evidence.
• Independent review reduces correlated mistakes but does not replace domain-specific security, legal, or production approval.