Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agent-sh/sync-docs
Sync documentation with code.
Passed 10 of 16 test cases with the skill, and 3 of 16 without it.
and 10 more in the full report
10 fixed4 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What specific section marker does the doc sync process check for inside CHANGELOG.md when auditing unreleased changes?
| Checked | Without skill | With skill |
|---|---|---|
| Searches CHANGELOG.md for a section titled ## [Unreleased] | Missed | Passed |
The instructions your model reads when the skill loads.
Unified skill for syncing documentation with code state. Combines discovery, analysis, and CHANGELOG update into a single workflow.
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const mode = args.find(a => ['report', 'apply'].includes(a)) || 'report';
const scope = args.find(a => a.startsWith('--scope='))?.split('=')[1] || 'recent';
const includeUndocumented = args.includes('--include-undocumented');
Step 1: Get changed files (use Bash):
# Recent changes (default scope)
git diff --name-only origin/main..HEAD 2>/dev/null || git diff --name-only HEAD~5..HEAD
# Or for all files
git ls-files '*.md'
Step 2: Find docs that reference changed files (use Grep):
*.md filesStep 3: Analyze each doc for issues:
Step 4: Check CHANGELOG:
## [Unreleased] sectionStep 5: If repo-map exists ({stateDir}/repo-map.json - platform state directory):
test cases passed, vs 3 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.