CtrlK
BlogDocsLog inGet started
Tessl Logo

akshay-babbar/doc-sync

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

1.59x
Quality

100%

Does it follow best practices?

Impact

86%

1.59x

Average score across 17 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-1/

Scenario: Rust new pub fn added with zero prior documentation

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.

Baseline (committed) state

src/lib.rs

pub fn add(a: i32, b: i32) -> i32 {
    a + b
}

README.md

# mathy

A tiny crate.

Working tree (current) state

A new public function is added without documentation.

src/lib.rs

pub 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 setup

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
}
EOF

Output spec

Check 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

criteria.json

task.md

README.md

SKILL.md

tessl.json

tile.json

TRUST.md