vibe-spec-sync SKILL.md skillA
vibe-spec-sync from ash1794/vibe-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ash1794/vibe-engineering/vibe-spec-sync@git:20261007.24cccadPins git:20261007.24cccad in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ash1794/vibe-engineering
- Path
plugins/vibe-engineering/skills/vibe-spec-sync/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261007.24cccad, committed Oct 7, 2026
- First version recorded
- Sep 25, 2026
- Size
- 8,686 bytes
- Repository stars
- 165
- License
- MIT
Keeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.
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
# vibe-spec-sync Code changes. Specs don't update themselves. This skill closes the loop. ## When to Use This Skill - **Audit mode**: implementation of a spec or design doc is claimed complete, after a major refactor, or when debugging behavior that may not match the spec - **Sync mode**: before committing, to detect spec drift from staged changes - **Sync mode**: after approving decisions (from `vibe-decision-journal`), to sync them back to the spec - Periodically, to confirm the spec still reflects reality ## When NOT to Use This Skill - No spec exists (write one first, or use `vibe-doc-quality-gate` to bootstrap) - Prototype/spike code with no spec commitment - Spec is explicitly labeled as aspirational/future-state - Code was intentionally diverged, with the reasons documented ## Modes ``` /vibe-spec-sync # Sync mode: staged changes vs spec (default) /vibe-spec-sync --audit # Audit mode: full spec vs implementation, no edits ``` ## Prerequisites The project must have: - A specification document (markdown) — configured in step 1 - Implementation code that the spec describes - Optionally: a test suite with requirement traceability markers (`# req:[ID]`) …
Read the whole file at its exact version.
How to install
mdr add ash1794/vibe-engineering/vibe-spec-sync@sha256:cdf00c6d602c46feThe line at the top of this page pins the label git:20261007.24cccad, 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_73xxmj6vz4ng5pwj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 25, 2026 and Oct 7, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.24cccad latest | 2026-10-07 | 24cccad | 8,686 B | A | view · diff |
| git:20260925.f6554ff | 2026-09-25 | f6554ff | 8,509 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 (8686 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
ash1794/vibe-engineering · 165 stars · license MIT · pushed 2026-10-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_73xxmj6vz4ng5pwj GET https://markdownregistry.com/api/v1/resolve?ref=ash1794/vibe-engineering/vibe-spec-sync GET https://markdownregistry.com/api/v1/blob/cdf00c6d602c46feca8517aab086c130081d5c354ad7c070d9261a1a1fc23316
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.