Auto-syncs stale docstrings and README when function signatures change. Detects documentation drift after refactors, parameter additions, or return type changes. Dry-run by default — proposes before writing.
87
100%
Does it follow best practices?
Impact
86%
1.59xAverage score across 17 eval scenarios
Passed
No known issues
{
"context": "Agent must propagate one documented API change across multiple markdown files that all mention the same symbol. Baseline models often update only the README and miss other markdown files.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Docstring updated",
"description": "The build_summary docstring includes documentation for the new include_archived parameter",
"max_score": 30
},
{
"name": "All markdown mentions proposed",
"description": "The report contains separate propose-only entries for README.md, docs/usage.md, and docs/reference.md",
"max_score": 55
},
{
"name": "Numbered entries present",
"description": "The report numbers the Updated/Would Update and Proposed entries so the user can select them by number",
"max_score": 45
},
{
"name": "Unified report format used",
"description": "The output contains '## Doc Sync Report' as the top-level heading",
"max_score": 45
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17