docs-sync — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited docs-sync (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Keep documentation and implementation aligned after user-facing code changes. Changed docs may define intended behavior that code needs to match.
Do not classify source of truth by edit order alone. Honor the current task's declared intent first: user request, issue, PR description, spec, implementation plan, tests, and repository guidance.
When declared intent conflicts with tests, build behavior, or security constraints, report the conflict before editing.
Default to a Docs Sync Report before edits unless the user explicitly asks for direct changes.
$docs-sync current branch: audit changed code/docs against the base branch.$docs-sync 문서 체크: audit docs intent against implementation.$docs-sync 코드 갱신 or $docs-sync 문서 기준: treat docs as intended behavior and report code gaps.$docs-sync 리포트만 or $docs-sync 리포트: audit only; do not edit docs or code.Read references/doc-coverage-checklist.md for audit targets, source-of-truth classification, report format, and patch guidance.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.