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

{
  "context": "Agent must handle a return type change when docstring and README describe the same symbol inconsistently: update the docstring to match the new return type, propose (not auto-write) the README update, and surface the discrepancy for human review.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Docstring return type updated",
      "description": "calculate_fee docstring return section references Decimal, not int/float",
      "max_score": 30
    },
    {
      "name": "README update proposed not auto-written",
      "description": "doc-sync-report.md contains a Proposed entry for README.md and README.md is unchanged on disk",
      "max_score": 55
    },
    {
      "name": "Conflict or inconsistency surfaced",
      "description": "The report flags [NEEDS HUMAN REVIEW] and notes that the docstring and README previously described calculate_fee inconsistently",
      "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