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 handle a large, noisy diff and identify exactly one in-scope documented contract change (parse_config gained strict) without producing false positives on other internal-only refactors.",
"type": "weighted_checklist",
"checklist": [
{
"name": "parse_config docstring updated",
"description": "parse_config docstring includes documentation for the strict parameter",
"max_score": 30
},
{
"name": "No false positives on other files",
"description": "The report does NOT propose or update docs for any file other than the one containing parse_config",
"max_score": 50
},
{
"name": "Noisy diff navigated correctly",
"description": "The report identifies exactly 1 symbol as in-scope — not 0 (missed it) and not 2+ (false positives)",
"max_score": 45
},
{
"name": "Unified report format",
"description": "doc-sync-report.md contains '## Doc Sync Report' as a 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