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
A Rust crate added a new public function. There was no prior documentation for it (no doc comment, no README mention). The skill must not invent documentation; it must report missing coverage only.
src/lib.rspub fn add(a: i32, b: i32) -> i32 {
a + b
}README.md# mathy
A tiny crate.A new public function is added without documentation.
src/lib.rspub fn add(a: i32, b: i32) -> i32 {
a + b
}
pub fn multiply(a: i32, b: i32) -> i32 {
a * b
}README.md (unchanged)# mathy
A tiny crate.git init
mkdir -p src
cat > src/lib.rs <<'EOF'
pub fn add(a: i32, b: i32) -> i32 {
a + b
}
EOF
cat > README.md <<'EOF'
# mathy
A tiny crate.
EOF
git add -A && git commit -m "baseline"
cat > src/lib.rs <<'EOF'
pub fn add(a: i32, b: i32) -> i32 {
a + b
}
pub fn multiply(a: i32, b: i32) -> i32 {
a * b
}
EOFCheck for any documentation that needs updating and write the results to doc-sync-report.md. It must list multiply under Missing Coverage and must not create any new doc comments.
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