oil-diff

Use when you want a visual HTML page that explains what a Git range, a commit, or uncommitted work changed, grouped into a few business items that a teammate who did not write the code can read. It is not for making the code changes themselves, committing, ordinary defect review, or generic slides.

Provide the target repository and the range or uncommitted work to explain. You may also provide genuine before-and-after screenshots from this change. You do not have to prepare the HTML page, the 3 to 7 business-item outline, or the .oil-diff data in advance. Documented needs are system git and Python 3.10 or newer; no API key is required. Those tools were not installed or run here.

The post introduces oil-diff in the first person and links the repository; a different t.co short URL in the long-form entities points at the same GitHub repo, and the post also has a video that was not watched. Ask for a report of the named range or uncommitted work. The documented flow collects deterministic Git data into .oil-diff/, groups files into 3 to 7 business items, builds diagrams or only verified screenshots, renders a single-file index.html, and lints until PASS while leaving git status unchanged. Documented commands were not executed here.

Do not run git add, commit, checkout, reset, or stash, and do not edit tracked files; output stays under untracked .oil-diff/ with a star-only gitignore. Screenshots must be live captures, user-provided for this change, or files in this diff; other images must not be copied in as if they were real. The author claims about quickly changing many files, and about a non-coding boss understanding the page at a glance, are not guarantees. The post video was not watched. Scripts were not executed. MIT requires notices and gives no warranty. GitHub login oil-oil and X handle I_am_oil_oil differ; the public mapping is submitted, not auto-approved.