layer-sync

仓库创建 2026年7月6日最近提交 21 天前SkillHot 收录 20 天前

▸ 精选理由

帮助发现重构或决策后未同步的差异，防止错误扩散。

这个 Skill 做什么

审计决策、文档、代码与报告间的一致性并报告漂移情况。

审计项目的知识层是否一致，把决策日志、规范/文档、代码和报告逐条对照，找出没有同步的改动（drift）。用在决策落地后、代码重构后或阶段收尾前，或有人问“文档和代码一致吗”的时候。它会给出文件:行级的证据并建议具体修补点，还能把文档锚定到源文件做精确检查。

▸ 展开 SKILL.md 英文原文

Use when checking whether the project's knowledge layers agree — the decision log, the spec/docs, the code, and the notebooks/reports — after a decision lands, after a refactor, before a phase closes, or when the user asks "is there drift", "did that decision propagate", "are docs and code in sync". Also use to register an explicit doc-to-source anchor link for point-precise checking. Trigger phrases: "sync check", "drift audit", "is the spec up to date with the code", "did D-numbers propagate", "link this doc to this source file".

研究检索层级同步文档代码一致漂移检测通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/huguryildiz/ALETHEIA/main/skills/core/layer-sync/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/huguryildiz/ALETHEIA/main/skills/core/layer-sync/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# layer-sync

A research project's knowledge lives in ordered layers — typically
`{{doc_layers}}` = decision log → spec/docs → code → notebooks/reports. Any change that
lands in one layer and not the others is *drift*, and drift silently corrupts the paper the
project is building toward. This skill audits a scoped slice of the layers, reports drift
with file:line evidence, and proposes exactly one next action. It never fixes anything in
the same turn.

## When to use

- After a decision-log entry lands (did it reach spec, code, notebooks?).
- After a commit range that touched a documented behavior.
- As a phase-gate step (the `phase-gate` skill calls this before closing).
- When any two laye

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有