code-sync SKILL.md skillA
code-sync from awrshift/agent-memory-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add awrshift/agent-memory-kit/code-sync@git:20261022.df602efPins git:20261022.df602ef in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- awrshift/agent-memory-kit
- Path
plugins/memory-kit/skills/code-sync/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261022.df602ef, committed Oct 22, 2026
- First version recorded
- Sep 17, 2026
- Size
- 8,114 bytes
- Repository stars
- 34
- License
- MIT
Reconcile the project's documents with what the code now shows, after a merge or at the end of a build: spec statuses (building → done only with a named gate, or → stale with the reason), assumed specs owed ratification, the project README map and its Last verified date. Surgical edits only. Use when the user says "/memory-kit:code-sync", "sync the docs", "sync specs with code", "синхронизируй доки с кодом", "что устарело в спеках", or right after merging an executor branch.
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
# /code-sync — documents reconciled against the repository
`close-session` reconciles the SESSION with memory. This reconciles a PROJECT's documents with
the CODE: every claim a spec still makes is checked against what is in the tree right now.
Two rails hold the whole skill up. **Evidence, never a claim** — a spec becomes `done` only from
a gate YOU ran in this session or a `Verified` cell someone already filled. **Surgical edits
only** — the only things you write are a status value, a `Verified` cell, one `Stale since:`
line, a map row, `Last verified:`, and a BACKLOG Done line. Everything else keeps its bytes.
## Step 0 — locate the projects
- `Glob projects/*/README.md`. If the repo keeps its documents elsewhere, read the root
`CLAUDE.md` / `README.md` for the docs home and use the map it names. Nothing found → say so
and stop. This skill never scaffolds.
- From each project README read two things: the map table ("Where this project's documents
live") — the SSOT for where plans, QA records and the backlog actually are — and the
`**Workflow tier:**` line, which sets how much evidence a `done` needs:
| Tier | Evidence a `done` needs |
|---|---|
…Read the whole file at its exact version.
How to install
mdr add awrshift/agent-memory-kit/code-sync@sha256:672fe99304f7fee2The line at the top of this page pins the label git:20261022.df602ef, 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_m63i6bhvfefhulve)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 17, 2026 and Oct 22, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.df602ef latest | 2026-10-22 | df602ef | 8,114 B | A | view · diff |
| git:20261007.2be0b0a | 2026-10-07 | 2be0b0a | 8,101 B | A | view · diff |
| git:20260925.d9398d8 | 2026-09-25 | d9398d8 | 8,107 B | A | view · diff |
| git:20260917.0e87591 | 2026-09-17 | 0e87591 | 7,838 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 (8114 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
awrshift/agent-memory-kit · 34 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m63i6bhvfefhulve GET https://markdownregistry.com/api/v1/resolve?ref=awrshift/agent-memory-kit/code-sync GET https://markdownregistry.com/api/v1/blob/672fe99304f7fee2608f5fdd646081065a0ee0c0ce4f4bb559a6a7967b7a3270
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.