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

{
  "context": "Agent must detect @deprecated decorator as a caller-visible contract change and update docstring while flagging README for human review. Baseline models often ignore decorators or over-rewrite README migration docs.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Deprecation documented in docstring",
      "description": "The fetch_user docstring is updated to indicate the function is deprecated and suggests using get_user instead",
      "max_score": 30
    },
    {
      "name": "README flagged for review",
      "description": "The report flags README.md mention of fetch_user as [NEEDS HUMAN REVIEW] and does NOT auto-rewrite it",
      "max_score": 50
    },
    {
      "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