docs-sync skillA
docs-sync is agent-read markdown (skill) from leeyudok/agents-scaffold: Bring documentation back in line with the code after changes to behavior, paths, versions, or generated output. Use on "update the docs", "refresh the README", "docs are stale", and right before opening a PR that changed any of those. Checks each documented claim against the actual code, command output, or official docs, and updates the parallel-language files together..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Documentation sync (docs-sync) Stale docs pass every automated gate. The link checker only sees broken links; the test suite never reads prose. So this is enforced as a procedure. ## Principles - **Verify claim by claim.** Do not skim for readability. Extract the **checkable claims** a sentence makes — paths, versions, numbers, behavior, defaults — and check each against reality. - **Never edit without evidence.** A `file:line`, a command's output, or an official-docs URL. What you could not confirm gets marked **"unverified"** rather than deleted — deleting it destroys the information. - **No optimistic wording.** If something only partly works, do not write that it "works". State what holds and what does not. ## Procedure ### 1. Extract the change surface ```bash git log --oneline <last-doc-commit>..HEAD git diff --stat <last-doc-commit>..HEAD ``` Keep only what documentation can be wrong about: CLI flags and defaults, paths, generated artifacts, versions, thresholds, gate behavior, support scope. ### 2. Collect the checkable claims Targets: `README*`, `AGENTS.md`, `CLAUDE.md`, per-directory `README.md`, skill/agent docs. ```bash …
Read the whole file at its exact version.
How to install
mdr add leeyudok/agents-scaffold/docs-sync@git:20260822.8e0b825mdr add leeyudok/agents-scaffold/docs-sync@sha256:f72f7e23d1287892Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_tiewe2276f4p2vka)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260822.8e0b825 latest | 2026-08-22 | 8e0b825 | 4,262 B | A | view · diff |
| git:20260822.f99046d | 2026-08-22 | f99046d | 4,186 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4262 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
leeyudok/agents-scaffold · 25 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tiewe2276f4p2vka GET https://markdownregistry.com/api/v1/resolve?ref=leeyudok/agents-scaffold/docs-sync GET https://markdownregistry.com/api/v1/blob/f72f7e23d128789269a19143345c07c987209790a03d0413501ed885ac91a05c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from leeyudok/agents-scaffold
Every file in leeyudok/agents-scaffold