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

{
  "context": "Tests the idempotency guard in apply mode. If the docstring already matches the changed signature, the skill should report it as already current or skip the write instead of duplicating entries.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "No duplicate parameter entry",
      "description": "src/cache.py contains exactly one region parameter line in the Args section",
      "max_score": 45
    },
    {
      "name": "Already current reported",
      "description": "doc-sync-report.md contains 'Already current' or a clear skip/no-op entry for fetch because the docstring already matches the signature",
      "max_score": 45
    },
    {
      "name": "Unified report format",
      "description": "doc-sync-report.md contains '## Doc Sync Report' as a top-level heading",
      "max_score": 45
    },
    {
      "name": "Apply mode declared",
      "description": "doc-sync-report.md contains 'Mode: apply'",
      "max_score": 45
    }
  ]
}

evals

README.md

SKILL.md

tessl.json

tile.json

TRUST.md