{"slug": "i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it", "title": "I wrote a script that counts the work AI-written commits cost you afterwards. It says 13 hours on my own repo.", "summary": "A developer built a read-only script that scans git history to quantify the review-and-retest debt left behind by model-written commits, checking whether each commit makes a promise (a test, issue, verification or follow-up) and whether the same file was touched again within 30 days. On the developer's own repository, all 9 commits were model-written, 8 carried no promise, and the tool tallied 13 hours of outstanding debt. The proposed fix attaches Owner, Promise and Verify-by fields to each change, running the check on the due date and logging red results to a plain-JSON ledger kept in the repo.", "body_md": "I build software — games, plugins, client work — and most of the code is written by a model and reviewed by me. Last night I wrote a read-only script that goes through git history and asks one question of every commit:\n\n**did anyone promise anything about this, and did anyone own it?**\n\nConcretely: does the message claim a test, an issue, a verification, a follow-up? And if the commit declares itself model-written, did the same file come back within 30 days?\n\nOn my own repository: 9 commits, all of them model-written, 8 of them with no promise attached at all, 13 hours of reading-and-retesting debt sitting there. I have an excuse of a kind — I wrote the tool last night — but the number is real and it is the kind of number I would not have believed from a landing page.\n\nSo the fix is deliberately small. A change carries three fields when it merges:\n\n```\nOwner: me\nPromise: the invoice PDF renders with a VAT line on a real client address\nVerify by: 2026-11-03\n```\n\nWhen the date arrives, it runs the check. Green closes it. Red puts the hours on a ledger you can look at — and, if it is a client's repo, an argument you can actually make.\n\nIt is one file, no account, and the ledger is plain JSON in your own repo. I'm not asking anyone to install anything. One thing instead: **say you want it and I'll run the scan on a repo of yours, read-only, and send you the number.** No install, nothing written to your repository, and if it says zero I'll say zero and you lose five minutes.\n\nWhatever comes back, I'll post the aggregate — including the null results.\n\nSource is on GitHub if you want to look at the logic before trusting the number.", "url": "https://wpnews.pro/news/i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it", "canonical_source": "https://dev.to/john_888/i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it-says-13-hours-on-2pi1", "published_at": "2026-10-18 12:42:29+00:00", "updated_at": "2026-10-18 12:46:53.383993+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents"], "entities": ["GitHub"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it", "markdown": "https://wpnews.pro/news/i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it.md", "text": "https://wpnews.pro/news/i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it.txt", "jsonld": "https://wpnews.pro/news/i-wrote-a-script-that-counts-the-work-ai-written-commits-cost-you-afterwards-it.jsonld"}}