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

criteria.jsonevals/scenario-6/

{
  "context": "Tests whether the agent proceeds to check for body-only documentation drift even when scripts/get_diff.sh exits with code 1 (no signature changes found). The function signature is unchanged so the script reports nothing — but the body changed and the docstring is now stale (says 'two conditions' when there are now four).",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Stale docstring updated",
      "description": "src/validator.py docstring no longer says 'two conditions' OR the doc-sync-report.md shows it was updated to reflect the four validation conditions",
      "max_score": 30
    },
    {
      "name": "Body-only drift detected",
      "description": "doc-sync-report.md contains an entry for validate_password indicating a docstring update — the agent did NOT stop after seeing no contract changes",
      "max_score": 30
    },
    {
      "name": "Not stopped at script exit",
      "description": "The report does NOT say 'No contract changes detected' as a final conclusion that stops processing — it proceeds to detect the body-only drift",
      "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

README.md

SKILL.md

tessl.json

tile.json

TRUST.md