AI Anonymous / Practical field guide / November 13, 2026

Still fits?

An AI assistant drafts a patch to change a timeout. Someone edits the same file before you apply it. Use Git to check whether the patch still fits, then refresh it around the newer settings.

In this field note · 6 sections
  1. Check the same patch against both files
  2. Refresh the patch against the current file
  3. Make it your own
  4. Use the check in your own repository
  5. Read the Git references
  6. Run the lab or share the field note

A patch can contain the right edit and still fail to apply. In this exercise, the requested change is a timeout of 5 to 10 seconds in a fictional help desk agent. A teammate changed the nearby review route after the patch was drafted. Git can spot the mismatch before it writes the file.

What we ran. Git for Windows 2.53.0.windows.1, two fictional settings files, and two handwritten patches. The lab runs offline and needs no repository setup.
AI Anonymous poster reading “Still fits?” A scratched brass template and matching cutout sit apart next to a brass caliper and curled shavings on a wooden bench. JABSystems.io appears below.
Original AI-generated artwork of a brass cutout, template, and caliper on a workbench.

01 / Reproduce

Check the same patch against both files

Install Git if needed. Extract the practice ZIP into a new folder outside any Git repository. Open PowerShell in the folder containing proposal.patch and run each line in order. -C makes Git run from the named subfolder, so the patch can find agent.conf there.

git -C original apply --stat ../proposal.patch
git -C original apply --check ../proposal.patch
$LASTEXITCODE
git -C current apply --check ../proposal.patch
$LASTEXITCODE

The stat shows one file with one insertion and one deletion. The original check prints nothing and returns 0. In the current folder, Git reports that the patch does not apply to agent.conf and returns a nonzero exit code. Both settings files keep their original bytes.

Open proposal.patch. The lines around the timeout edit tell Git where the edit belongs. One of those context lines says route=review. The newer file says route=manual-review in that spot.

02 / Inspect

Refresh the patch against the current file

Open refreshed.patch and check its intent. Its context now includes the current route. The only added and removed settings lines still change the timeout from 5 to 10.

@@ -2,7 +2,7 @@
 mode=draft
 route=manual-review
 format=text
-timeout_seconds=5
+timeout_seconds=10
 retries=0
 log=local
 approval=required

Run the check against the current copy, then apply the reviewed patch inside the disposable fixture if Git reports success.

git -C current apply --check ../refreshed.patch
if ($LASTEXITCODE -eq 0) {
    git -C current apply ../refreshed.patch
}
Get-Content ./current/agent.conf

In the resulting file, route=manual-review stays in place and timeout_seconds=10 appears. Re-extract the practice ZIP into a fresh folder to run the full exercise again.

03 / Make it your own

Change a line outside the patch

  1. Copy the original folder to a new folder named adapted.
  2. In adapted/agent.conf, change the last line to owner=operations. Save with LF line endings.
  3. Run the original check against that folder. Compare the exit code with the check against current.
git -C adapted apply --check ../proposal.patch
$LASTEXITCODE

The check returns 0. In this fixture, owner is outside the edited lines and their context. Use that distinction to decide which parts of a real patch deserve closer review as the underlying files evolve.

Boundaries

Use the check in your own repository

From the repository root, inspect which files the proposed patch touches and read its edits. Run git apply --check path/to/proposal.patch against the working tree you intend to change. If the check fails, start from the current source and make a fresh diff after reviewing the edit. Git can write that diff directly with git diff --output=proposal.patch -- path/to/file when the tracked file has an unstaged edit.

A passing check answers whether Git can apply the patch to the current files. Run the relevant project tests after applying it to verify the requested behavior. This lab exercised applicability and the resulting fixture bytes. Model output, agent behavior, and performance were outside the exercise.

Primary sources / Checked November 13, 2026

Read the Git references

Downloads / Practice and social files

Run the lab or share the field note

Explore more AI Anonymous field notes →

Share this post.

Found this useful? Pass it along. Download the artwork, add your own take, and tag @jabsystems.io so I can see your post.