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-4/

{
  "context": "Agent must propagate one documented API change across multiple markdown files that all mention the same symbol. Baseline models often update only the README and miss other markdown files.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Docstring updated",
      "description": "The build_summary docstring includes documentation for the new include_archived parameter",
      "max_score": 30
    },
    {
      "name": "All markdown mentions proposed",
      "description": "The report contains separate propose-only entries for README.md, docs/usage.md, and docs/reference.md",
      "max_score": 55
    },
    {
      "name": "Numbered entries present",
      "description": "The report numbers the Updated/Would Update and Proposed entries so the user can select them by number",
      "max_score": 45
    },
    {
      "name": "Unified report format used",
      "description": "The output contains '## Doc Sync Report' as the top-level heading",
      "max_score": 45
    }
  ]
}

evals

README.md

SKILL.md

tessl.json

tile.json

TRUST.md