Your AI Reads Your Docstrings. Are They Right?

Copilot, Claude Code, Cursor — they all read your docstrings to understand your code. When those docstrings are wrong, your AI makes confident, wrong suggestions. And wrong docs are worse than no docs. Studies show incorrect documentation drops LLM task success by 22 percentage points compared to correct docs. Your linter checks style . But who checks that the docstring is actually accurate ? The gap in your toolchain Existing tools cover the basics: ruff — docstring style and formatting interrogate — docstring presence But neither checks whether your docstring matches the code . A function that raises ValueError but doesn't document it. A parameter added last sprint but missing from the docstring. Code that changed but the docstring didn't. That's layers 3–6 of docstring quality — and nothing was checking them. docvet fills that gap docvet is a CLI tool that vets docstrings across six quality layers: Layer Check What it catches Presence docvet presence Public symbols with no docstring