In a repo worked on by AI coding agents, the docs have an unusual reader. Each new session starts cold, reads AGENTS.md, the design notes and the skills,…

In a repo worked on by AI coding agents, the docs have an unusual reader. Each new session starts cold, reads AGENTS.md, the design notes and the skills, and then builds on what it read. So a doc is not only for people: it is input to the next piece of code, and a wrong sentence in it becomes a wrong assumption in new work.

Yonto Player's repo has one rule for this, at the top of AGENTS.md: docs change in the same pull request as the code, never as a follow-up. This post is about the rule and the small habits around it. The rule The wording in the repo is short. docs/, AGENTS.md and skills/ are what the next session reads, so a change whose docs are not written is unfinished. "Unfinished" is the useful word.

A follow-up PR for docs is a promise that no build checks. If the docs are part of the definition of done, the reviewer sees the code and the prose it changes in one diff, and "did the docs change?" has an answer on the page. The scope is deliberate. You update the docs that the change invalidates, and you find them by searching the subject across the whole repo.

The aim is not to polish documentation, it is to keep it describing what the code does. Name the sentence the change makes false The PR skill in the repo (skills/open-a-pr) adds a step before you write the description. In my words: state in one sentence what this change makes false, then find every copy of that sentence. The skill spells out the method: Search for the subject, not the wording.

You cannot guess how someone else phrased a claim, so search for the thing the claim is about, using a few generic words for it, and read every hit. Read the file you edited first. It is the place you were already writing in, and the easiest to check. Change every copy. If a claim lived in two files, both change in the same PR, so the docs agree with each other. Check a correction the same way.

Source disclosure

This is a source-linked briefing. Read the original report from Dev Community .