hyper-docs-sync SKILL.md skillA
hyper-docs-sync from zeikar/hyperclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zeikar/hyperclaude/hyper-docs-sync@git:20260813.106ef76Pins git:20260813.106ef76 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zeikar/hyperclaude
- Path
skills/hyper-docs-sync/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260813.106ef76, committed Aug 13, 2026
- First version recorded
- May 10, 2026
- Size
- 5,776 bytes
- Repository stars
- 4
- License
- MIT
Use after implementation changes documented API, schemas, CLI flags, or architecture — before docs go stale. Also when the user invokes /hyperclaude:hyper-docs-sync. Syncs docs to the current code state.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# hyper-docs-sync
Documentation sync gate. Reads recent code changes, maps them to documentation files via the project's mapping table (or heuristic fallback), and dispatches the `documenter` agent to update each affected doc — creating new docs as needed.
## When to use
- User typed `/hyperclaude:hyper-docs-sync`.
- After non-trivial implementation that changes documented API, CLI flags, data models, or architecture.
## When to skip
- Pure refactors with no behavioral change.
- Changes already reflected in docs.
## How to invoke
**Invocation argument:** $ARGUMENTS
Narrow contract (same shape as `hyper-code-review`):
| Pattern | Meaning |
|---|---|
| Empty | Changes since `main` (`git diff main...HEAD`) |
| Literal `uncommitted` | Staged + unstaged + untracked working-tree changes |
| 7-40 hex chars matching `^[0-9a-f]{7,40}$` | That specific commit (`git show --format= --patch <sha>`) |
| `^vs (.+)$` where the rest matches `^[A-Za-z0-9._/-]+$` | Changes since that ref (`git diff <ref>...HEAD`) |
| Anything else | Tell user the contract above, ask to clarify, STOP. |
### Step 1 — Resolve changed files + their diffs
Use the Bash tool. Concrete commands per scope:
…Read the whole file at its exact version.
How to install
mdr add zeikar/hyperclaude/hyper-docs-sync@sha256:955071e2bd460842The line at the top of this page pins the label git:20260813.106ef76, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mcb7pa7xrhujaztl)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 10, 2026 and Aug 13, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260813.106ef76 latest | 2026-08-13 | 106ef76 | 5,776 B | A | view · diff |
| git:20260704.8702146 | 2026-07-04 | 8702146 | 5,640 B | A | view · diff |
| git:20260520.07f0607 | 2026-05-20 | 07f0607 | 5,468 B | A | view · diff |
| git:20260512.7c7b834 | 2026-05-12 | 7c7b834 | 5,555 B | A | view · diff |
| git:20260510.0127b21 | 2026-05-10 | 0127b21 | 5,612 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 (5776 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
zeikar/hyperclaude · 4 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mcb7pa7xrhujaztl GET https://markdownregistry.com/api/v1/resolve?ref=zeikar/hyperclaude/hyper-docs-sync GET https://markdownregistry.com/api/v1/blob/955071e2bd4608429996fe6ca90e4eb9c9b75e0fb852d6a6f56408479017b284
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.