Back to Details

workbench-hermes-docs-sync

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Workbench Hermes Docs Sync

Workbench Hermes 文档同步

Hermes is the second-pass reviewer for public-facing workbench documentation. Claude Code writes the first draft or patch. Hermes reviews it for coverage, consistency, public safety, and installability before sync or publish.
Hermes是面向公众的工作台文档的第二轮审核者。Claude Code撰写初稿或补丁。Hermes在同步或发布前审核其覆盖范围、一致性、公共安全性和可安装性。

Core Rule

核心规则

Claude writes. Hermes reviews. Supervisor accepts.
Hermes should not turn a docs-sync review into a rewrite unless the existing draft is materially wrong. Its job is to find every related public surface that must change, then return a bounded patch plan or PASS/FLAG/BLOCK verdict.
Claude撰写，Hermes审核，负责人批准。
除非现有初稿存在实质性错误，否则Hermes不应将文档同步审核变成重写工作。其职责是找出所有必须变更的相关公开内容，然后返回一个明确的补丁计划或PASS/FLAG/BLOCK Verdict。

When To Use

使用场景

Use this for:
  • skill additions, renames, removals, or registry-facing skill-map changes;
  • public README, docs map, agent roster, issue-template, autopilot, or install instruction changes;
  • Super.engineering/Hermes upstream speed-match docs;
  • any change that says "sync this everywhere", "public-facing", "skills.sh", "all Hermes", or "docs-sync";
  • release notes or PR text that must remain evidence-backed and public-safe.
Do not use this for private scratch notes, raw run logs, uncommitted screenshots, or live runtime mutation.
适用于以下情况：
  • skill的新增、重命名、移除，或面向注册表的skill-map变更；
  • 公开README、文档地图、agent名单、issue-template、autopilot或安装说明变更；
  • Super.engineering/Hermes上游速度匹配文档；
  • 任何标注“同步至所有位置”“面向公众”“skills.sh”“所有Hermes”或“docs-sync”的变更；
  • 必须基于证据且符合公共安全要求的发布说明或PR文本。
不适用于私人草稿笔记、原始运行日志、未提交的截图或实时运行时修改。

Public Surface Sweep

公开内容排查

Hermes must check all potentially related public surfaces, not only the touched file:
  • README.md
    : install count, public overview, docs map, runtime model, Chinese overview when relevant.
  • AGENTS.md
    : read order, operating rules, file map, validation command list.
  • SYNTHESIS.md
    : current strategy when the change alters operating model.
  • DECISIONS.md
    : durable rationale for behavior-changing workflow changes.
  • skills/README.md
    : registry-facing skill list and install instructions.
  • skills/*/SKILL.md
    : affected skill contracts and cross-skill references.
  • docs/*.md
    : lane docs, public contracts, public-safe evidence boundaries.
  • agents/**/*.md
    : Hermes, Claude, Codex, remote, or reviewer role bindings.
  • issue-templates/
    and 
    autopilots/
    : reusable entry points affected by the new workflow.
If a surface is checked and not changed, name it in the review with "no change needed" and the reason.
Hermes必须检查所有潜在相关的公开内容，而不仅仅是被修改的文件：
  • README.md
    ：安装次数、公开概述、文档地图、运行时模型，相关时需检查中文概述。
  • AGENTS.md
    ：阅读顺序、操作规则、文件地图、验证命令列表。
  • SYNTHESIS.md
    ：当变更改变操作模型时，需检查当前策略。
  • DECISIONS.md
    ：影响行为的工作流变更的持久化依据。
  • skills/README.md
    ：面向注册表的skill列表及安装说明。
  • skills/*/SKILL.md
    ：受影响的skill契约及跨skill引用。
  • docs/*.md
    ：分支文档、公开契约、符合公共安全要求的证据边界。
  • agents/**/*.md
    ：Hermes、Claude、Codex、远程或审核者角色绑定。
  • issue-templates/
    和 
    autopilots/
    ：受新工作流影响的可复用入口点。
如果某个内容已检查且无需变更，需在审核中注明“无需变更”并说明原因。

Review Loop

审核流程

  1. Read the Claude-authored diff first.
  2. Identify the behavior or public promise that changed.
  3. Sweep the public surfaces above using file search and direct reads.
  4. Flag stale install counts, dead links, missing skill-map rows, inconsistent role binding, or private/internal evidence leaking into public docs.
  5. Recommend the smallest patch set.
  6. Return a verdict. Do not silently mutate live Multica/Hermes runtime config.
Useful commands:
bash
git diff --name-only
git diff --check
rg -n "skill-name|lane-name|Hermes|Claude Code|skills.sh|install" README.md AGENTS.md SYNTHESIS.md DECISIONS.md docs skills agents issue-templates autopilots
  1. 首先阅读Claude撰写的差异内容。
  2. 识别已变更的行为或公开承诺。
  3. 使用文件搜索和直接阅读排查上述所有公开内容。
  4. 标记过期的安装次数、失效链接、缺失的skill-map条目、不一致的角色绑定，或泄露到公开文档中的私有/内部信息。
  5. 推荐最小化的补丁集合。
  6. 返回Verdict。请勿静默修改实时Multica/Hermes运行时配置。
实用命令：
bash
git diff --name-only
git diff --check
rg -n "skill-name|lane-name|Hermes|Claude Code|skills.sh|install" README.md AGENTS.md SYNTHESIS.md DECISIONS.md docs skills agents issue-templates autopilots

Verdict Contract

Verdict规范

Return:
text
HERMES_DOCS_SYNC_REVIEW
source_author: Claude Code | other
changed_behavior:
public_surfaces_checked:
required_patches:
no_change_needed:
public_safety:
installability:
verification:
residual_risk:
VERDICT: PASS | FLAG | BLOCK
Use 
PASS
only when every related public surface is either updated or explicitly judged unchanged. Use 
FLAG
when publishable but missing optional proof. Use 
BLOCK
when stale public instructions, broken install paths, private data exposure, or role-binding drift would mislead future users or agents.
返回如下内容：
text
HERMES_DOCS_SYNC_REVIEW
source_author: Claude Code | other
changed_behavior:
public_surfaces_checked:
required_patches:
no_change_needed:
public_safety:
installability:
verification:
residual_risk:
VERDICT: PASS | FLAG | BLOCK
仅当所有相关公开内容已更新或被明确判定无需变更时，使用
PASS
。当内容可发布但缺少可选证明时，使用
FLAG
。当存在过期的公开说明、损坏的安装路径、私有数据泄露或角色绑定偏移，可能误导未来用户或agent时，使用
BLOCK
。

Common Failure Modes

常见失败模式

  • Only updating 
    skills/README.md
    and forgetting README install count.
  • Adding a workflow doc without a decision record.
  • Adding a skill but not binding it to the Hermes role that should use it.
  • Treating Discord/terminal screenshots as public proof.
  • Updating AGENTS read order but forgetting the file map or validation list.
  • Letting Hermes rewrite the whole doc instead of reviewing the Claude draft.
  • 仅更新
    skills/README.md
    而忘记更新README中的安装次数。
  • 添加工作流文档但未添加决策记录。
  • 添加skill但未将其绑定到应使用它的Hermes角色。
  • 将Discord/终端截图作为公开证明。
  • 更新AGENTS阅读顺序但忘记更新文件地图或验证列表。
  • 让Hermes重写整个文档而非审核Claude的初稿。