AI Blocks › Write down how work gets done
Monthly developer documentation review
Share your docs and recent changes. Get stale pages fixed, broken steps flagged and a clearer start guide.
Monthly developer documentation review is a free AI agent for the job "Write down how work gets done". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks · Thinking: high
What it does
Developer docs rot one commit at a time. A flag gets renamed and the README still shows the old one. An endpoint gains a field the spec never heard of. The changelog stops at a version from spring. The first person to notice is the new developer on their first morning, and they assume the problem is them. This agent reads the repo every month. It tries each README step on a fresh machine and marks what broke, with proof and the edit. It maps which doc describes which code, so this month's changed files point at the docs to re-check, and lists the modules with no doc at all. It drafts the changelog from what was released, in plain words, and proposes rewrites for docstrings, the API spec and the glossary where they drifted. Every change is a proposal. It never commits, merges or publishes.
You give it
- Your repo with its README, docs, changelog, API spec and the month's git history
- Docs that live outside the repo, such as a wiki page (optional)
- The release tags for the month (advised)
- Last month's keeper file, once it exists
- A buyer brief (optional)
- Your question (optional)
You get
- Each README step marked working or broken, with proof and the edit
- Every doc that disagrees with the code, with file and line
- New modules and endpoints with no doc
- A changelog draft for the month's releases, grouped into added, changed and fixed
- Proposed rewrites for docstrings, the API spec and the glossary
- A map of which doc covers which code, kept current
Use it when
- Other people build on or install your code and keep hitting the same broken step.
- Your changelog stopped months ago and the spec does not match the API.
- You want docs checked on a schedule instead of when someone complains.
How to use it
- Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then point it at the repo.
- Tell it which releases shipped this month, or let it read the tags.
- Read the broken README steps first. Fix those before anything else.
- Review the proposed rewrites and the changelog draft. Commit and publish what you approve yourself.
- Run it again on the first Tuesday of next month. It re-tests what you fixed.