Documentation Review changes

Review changes

Prepare the exact change you want reviewed.

Your Git command defines the review boundary. Inspect the output before submitting confidential source code.

Common Git commands

Three lines of context are sufficient for parsing and line anchoring. Add context snippets separately when the finding depends on surrounding code.

shell 
# Uncommitted changes
git diff --unified=3

# Staged changes
git diff --cached --unified=3

# Current branch against origin/main
git diff --unified=3 origin/main...HEAD

What makes a valid diff

Submit unified Git diff or patch text rather than a source file or prose description.

  • Include old and new file headers such as --- and +++.
  • Include at least one hunk header in the @@ ... @@ form.
  • Preserve newlines when placing the diff inside JSON.

Repository and pull-request boundary

The caller retrieves the change

If your client already has pull-request context, it can produce a diff with a trusted provider tool and submit that text. Enjoyable does not fetch the pull request itself.

Documentation