Free tool: runs in your browser
AI-assisted change description builderwhen an AI tool helped with your pull request
TimeBinder adds a layer of protection against AI and human fraud and disputes. Say what the AI tool did, what you checked and what you wrote yourself. You get a pull request description, a commit note and a list of gaps.
Everything you type stays on this page. This page cannot see your code and cannot tell whether an AI tool wrote any of it. Only you can say what you did. Follow your project’s own rules. It is not legal advice, and it does not check licences.
Write your description
Name the tool, tick what it did and what you did, and say how you tested. Nothing you type is sent to TimeBinder.
Everything you type stays on this page. Nothing is sent anywhere or tied to your name.
Write a clear note for a pull request or patch that used an AI tool
Say what the AI tool did, what you checked and what you wrote yourself. You get a pull request description, a short commit message note and a list of gaps. It cannot see your code or tell whether a tool wrote it.
How should I describe a pull request that used an AI tool? The short answer
Say which tool you used, what it did (first draft, tests, documentation, finding the bug, or only an idea), how much of the change came from it, and what you did yourself: read every line, built it, ran the tests, and can explain every change. Add a sentence on how you tested. Check the project’s contributing file first, because projects differ. Some ask for a note in the description, some ask for a tag or trailer in the commit, some limit AI-written changes and some ban them.
A human, not a tool, should add any sign-off or certificate a project requires. If an AI tool wrote the description or commit message, say so and check every claim in it. A TimeBind of your final files can show the exact files existed no later than a recorded time. It does not show how they were written.
Why this came up in November 2026
How to disclose AI use in code changes is a live argument among developers. Counts below were read on 13 November 2026 (Australia/Brisbane) unless the text says another date. Pivot to AI’s “Linux kernel goes full AI slop, hides chatbot commits”, uploaded on 14 October 2026, showed 152,281 views and 5,264 likes. SavvyNik’s “Linux and OSS Maintainers Are Drowning in AI Slop”, uploaded on 21 October 2026, showed 25,479 views. These are demand signals for the topic. This page does not check the claims in either video.
A report on XenoSpectrum, published on 24 October 2026, said the Linux kernel removed its requirement for an Assisted-by tag, and that about 10 percent of the 18,533 unmerged commits it counted through Linux 7.3-rc7 carried the tag. The same report said the rule that a human must sign off, and the rule that maintainers may reject a patch the sender cannot explain, stayed. We cite that report for the facts it states and have not checked them against the kernel documentation ourselves.
The practical point for a contributor is to tell reviewers what they need to judge the change, in whatever form the project asks. For the maintainer side, see the vibe coding review checklist.
What this tool does and does not do
The honest job of this page is to help you give reviewers the facts. See also the glossary entries for existed no later than and SHA-256.
| Part | What it does | What it does not do |
|---|---|---|
| Pull request description | Writes a Markdown note with the tool, what it did, how much it produced, what you did and how you tested. | See your code or check that the note is true. |
| Commit note | Writes a short line for the commit message, and a trailer only if you say your project asks for one. | Know the exact format your project wants. |
| Gaps | Flags things reviewers will ask about, such as not reading every line or no test described. | Tell whether an AI tool wrote the change. |
| A TimeBind of a file you already hold | Records that an exact file existed no later than a recorded time and still matches, using a SHA-256 fingerprint made in your browser. The file stays on your device. | Show how a file was written, or who wrote it. |
If you may need to show your files later
For a change you may need to defend later:
- Save the final branch contents or the patch file you sent, with your description.
- Make a TimeBind of each exact file you already hold. The fingerprint is made in your browser and the file stays on your device. You can later download a Proof of Time Certificate.
- Keep your prompts or chat log if you want to show how the work went.
A TimeBind shows the exact file existed no later than the recorded time and still matches. It does not show that a human or a tool wrote it.
First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15.
What a TimeBind shows, and what it does not. It shows that an exact file existed no later than a recorded time and that a copy shown later still matches its fingerprint. It does not show who made the file, who owns it, that its contents are true, or whether AI was used to make or edit it. This is general information, not legal advice.
AI-assisted change description builder: FAQ
Can this tool tell whether code was written by an AI tool?
No. It cannot see your code. It writes down what you tell it.
Do I have to add a tag or trailer to my commit?
Only if your project asks. Some projects have dropped tag requirements and prefer a note in the description. Read the project’s contributing file.
Can I let an AI tool sign off my commit?
No. Sign-off or certificate lines are for a human who takes responsibility. Never add one on a tool’s behalf.
Does disclosing AI use protect me if the change is rejected?
No. A good description helps reviewers, but a project can still decline a change.
Does this check licences?
No. Tick the licence line only if you checked. The tool flags it if you did not.
Is anything I type or tick sent to TimeBinder?
No. This page runs in your browser. What you type stays on the page.
Related guides and tools
- Vibe coding review checklistReview code before you send it
- AI coding assistant settings file secrets checklistKeep secrets out of tools
- Open source license change record checklistRecord a licence change
- SHA-256 file hash checkerCheck a file fingerprint
- GlossaryPlain definitions of fingerprint, SHA-256 and existed no later than
- All free toolsPrivate, in-browser tools
Date the exact files you already hold
Add a layer of protection against AI and human fraud and disputes: a dated, checkable record of the exact files you submitted.
- Open the app and sign in with email or Google.
- Add your files. They stay on your computer.
- Seal them and download your Proof of Time certificates.
First Pooled TimeBind free, no card, then from US$5. See pricing.