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": "Tests the idempotency guard in apply mode. If the docstring already matches the changed signature, the skill should report it as already current or skip the write instead of duplicating entries.",
"type": "weighted_checklist",
"checklist": [
{
"name": "No duplicate parameter entry",
"description": "src/cache.py contains exactly one region parameter line in the Args section",
"max_score": 45
},
{
"name": "Already current reported",
"description": "doc-sync-report.md contains 'Already current' or a clear skip/no-op entry for fetch because the docstring already matches the signature",
"max_score": 45
},
{
"name": "Unified report format",
"description": "doc-sync-report.md contains '## Doc Sync Report' as a top-level heading",
"max_score": 45
},
{
"name": "Apply mode declared",
"description": "doc-sync-report.md contains 'Mode: apply'",
"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