A clearer sentence can hide a changed commitment.
An AI-assisted rewrite deserves the same review as any proposed edit. Compare the revision with the original before you accept it, especially when the text contains dates, responsibilities, or approval conditions.
Our fictional request is narrow: rewrite only the first sentence for clarity. Keep the owner Casey, Friday review date, and human-approval condition. The exercise includes an original and two revisions authored by us to make the differences visible. None of these documents is an AI model output.
The draft is very hard to read.
Owner: Casey.
Review date: Friday, October 16, 2026.
Human approval required before publication.
One revision changes only the opening sentence. The other also replaces Casey with Jordan, moves the review from Friday to Thursday, and removes the approval requirement. This teaches a review habit; it does not show how often an AI system makes those changes.
Keep two files, not two memories.
Use an empty practice folder and PowerShell. If needed, install Git for Windows from its official project, reopen PowerShell, and check:
git --versionWe tested these comparisons on Windows with git version 2.53.0.windows.1. You do not need to initialize a repository for this exercise. Save text as plain UTF-8 files. Git does not provide a readable prose comparison of a Word document or PDF through these commands.
For your own draft, preserve the original and save the proposed rewrite under a different name. The comparisons below read the files without applying the revision. Keep the instruction that defined the intended change alongside them.
Inspect the exercise before running it.
Download the exercise ZIP, extract it, and read the scope and files:
Invoke-WebRequest -Uri 'https://jabsystems.io/ai-anonymous/Social/review-the-ai-edit-exercise.zip' -OutFile .\edit-exercise.zip
Expand-Archive -LiteralPath .\edit-exercise.zip -DestinationPath .\exercise
Get-Content -LiteralPath .\exercise\edit-scope.txt
Get-Content -LiteralPath .\exercise\edit-original.md
Get-Content -LiteralPath .\exercise\edit-out-of-scope.mdThe ZIP contains the three drafts, scope, README, observed comparisons, and an optional untested prompt. No executable script is included. Installing Git and downloading the files require network access; the subsequent comparisons make no AI or network request.
Read the removed line beside its replacement.
git --no-pager diff --no-index --no-ext-diff --no-textconv --no-color -- .\exercise\edit-original.md .\exercise\edit-out-of-scope.md
$LASTEXITCODEThe Git diff reference documents --no-index for comparing filesystem paths. --no-pager keeps this small exercise in the terminal; the other options disable external diff helpers, text conversion, and color.
In the patch body, a minus marks an old line; a plus marks a new one. File-header lines beginning --- and +++ identify the compared paths. Here is the observed changed block, with file headers omitted:
@@ -1,4 +1,4 @@
-The draft is very hard to read.
-Owner: Casey.
-Review date: Friday, October 16, 2026.
-Human approval required before publication.
+The draft needs clearer wording.
+Owner: Jordan.
+Review date: Thursday, October 15, 2026.
+Ready to publish.Only the first replacement fits the request. The owner change, date change, and removed human-approval requirement need a decision from the responsible person. Read the complete revision too: a diff can focus your attention on changes while leaving a pre-existing mistake untouched.
Use a second view when a long line hides a small edit.
git --no-pager diff --no-index --no-ext-diff --no-textconv --no-color --word-diff=plain -- .\exercise\edit-original.md .\exercise\edit-out-of-scope.md
$LASTEXITCODEPlain word diff marks removed words with [- -] and added words with {+ +}. The observed owner and date lines are:
Owner: [-Casey.-]{+Jordan.+}
Review date: [-Friday,-]{+Thursday,+} October [-16,-]{+15,+} 2026.Words normally follow whitespace boundaries. If the input itself contains these delimiter sequences, this presentation can be ambiguous. Use the full line comparison and complete source files to resolve it. The command exposes text changes; it does not interpret their business meaning.
Changed does not mean wrong. Unchanged does not mean true.
git --no-pager diff --no-index --no-ext-diff --no-textconv --no-color -- .\exercise\edit-original.md .\exercise\edit-in-scope.md
$LASTEXITCODE
git --no-pager diff --no-index --no-ext-diff --no-textconv --no-color -- .\exercise\edit-original.md .\exercise\edit-original.md
$LASTEXITCODEThe in-scope revision returned 1, just like the out-of-scope revision. Comparing the original with itself returned 0 and no diff output. With --no-index, these statuses indicate differences or no differences; they do not certify scope, factual accuracy, or approval.
Read $LASTEXITCODE immediately after each Git command. If Git reports a missing file or another runtime error, resolve that error before interpreting a status. A failed comparison is not evidence that a revision passed review. Our Git configuration also printed line-ending warnings; the source-file hashes were unchanged after comparison.
Download the four observed comparison reports. The reports preserve commands, statuses, output, and Git version. They describe only our authored fixture files.
Let a model propose. Keep acceptance deliberate.
- Define the allowed change. Identify which sentence, field, or file may change and which facts must remain.
- Keep the original. Save the proposal separately so review has a stable baseline.
- Inspect each change. Pay special attention to dates, names, numerical values, qualifiers, and approval language.
- Verify the meaning. Consult the authoritative source or responsible person when a change alters a commitment.
- Accept deliberately. Retain the reviewed revision and the scope record. A changed-file status alone is insufficient.
The optional starter prompt requests a one-sentence edit and preserved fields. It was not executed. A model-generated change summary would be another claim to check against the files; it would not replace the comparison.
If you already work in a Git repository, Pro Git explains the difference between working changes and staged changes. git diff shows unstaged tracked changes; git diff --staged shows staged changes. New untracked files need separate inspection. Review the relevant files before committing an AI-assisted coding change.
A review aid, with human decisions still visible.
Actually verified: four comparisons on Windows with git version 2.53.0.windows.1: line comparisons of both revisions, a word comparison of the out-of-scope revision, and an identical-file comparison. Observed exits were 1 / 1 / 1 / 0. We checked the owner/date/approval differences, package integrity, and website downloads.
Not tested: model execution, model output quality, automatic scope enforcement, production agent behavior, speed, savings, other operating systems, binary-document conversion, or confidential data. A diff cannot prove a fact is correct or that a change is authorized. It compares the saved files you supply; it cannot reconstruct a lost original.
This local comparison workflow does not upload the drafts. Sending your own material to an AI service would be a separate action governed by that service and your data permissions. A prompt does not enforce access or tool permissions.
Primary sources were reviewed October 13, 2026. This is a practical use of established Git functionality, not a claim that it was released today.
Keep the walkthrough and the practice files together.
Primary sources: Git diff reference, Pro Git: recording changes, and Git for Windows.
Exercise ZIP · Original graphic · Caption · Alt text · Posting ZIP
Manual social delivery: graphic, teaser, alt text, and article URL are prepared for the user to post. Nothing is scheduled or published to social media; no Instagram profile-link change is claimed.