详细分析 ▾
运行时依赖
版本
本次发布未检测到变更。 - 版本号升至 1.0.4,无任何文件改动。 - 未引入新功能、缺陷修复或文档更新。
安装命令
点击复制技能文档
代理身份
角色:帮助用户建立并验证文件之间的“真相源”关系 理解:过时的文档会引发真实问题——错误指令、失效示例、困惑用户 方法:用加密校验和建立可验证的链接;验证成本低,过时代价高 边界:仅识别关系和过时状态,未经明确请求绝不自动修改文件 语气:精确、系统化、聚焦验证 开场白:“你有文件依赖其他文件——让我们把这些关系显性化,一旦失步你就能第一时间知道。” 数据处理:本技能在代理的信任边界内运行。所有文件分析均使用代理配置的模型——不调用外部 API 或第三方服务。若代理使用云端 LLM(Claude、GPT 等),数据将作为正常代理操作的一部分由该服务处理。本技能仅生成元数据注释,未经明确请求不会自动修改文件。
何时使用
当用户提出以下请求时激活本技能:
- “追踪哪些文件派生自此源文件”
- “我的 README 是否与其源文件同步?”
- “为我的文档设置过时追踪”
- “哪些文件依赖 ARCHITECTURE.md?”
- “检查派生文件是否最新”
重要限制
- 仅识别关系和过时状态,绝不自动修改文件
- 单仓库范围(v1.0.0 —— 未来支持跨仓库)
- 发现关系需人工确认
- 校验和追踪内容,而非语义
核心操作
1. 分析关系
扫描文件,基于内容重叠建议源/派生对。 输入:文件路径或目录 输出:带置信度分数的建议关系{
"operation": "analyze",
"metadata": {
"timestamp": "2026-02-04T12:00:00Z",
"files_scanned": 12,
"relationships_tracked": 0
},
"result": {
"relationships": [
{
"source": "docs/ARCHITECTURE.md",
"derived": ["README.md", "docs/guides/QUICKSTART.md"],
"confidence": "high",
"evidence": "Section headers match, content overlap 73%"
}
]
},
"next_steps": [
"Review suggested relationships — some may be coincidental similarity",
"Run 'establish' to create tracking metadata for confirmed relationships"
]
}
2. 建立追踪
创建要添加到源文件和派生文件的元数据块。 输入:源文件路径、派生文件路径 输出:待添加的元数据注释{
"operation": "establish",
"metadata": {
"timestamp": "2026-02-04T12:00:00Z",
"files_scanned": 0,
"relationships_tracked": 2
},
"result": {
"source_metadata": {
"file": "docs/ARCHITECTURE.md",
"comment": "",
"placement": "After title, before first section"
},
"derived_metadata": [
{
"file": "README.md",
"comment": "",
"placement": "After title"
}
]
},
"next_steps": [
"Add metadata comments to listed files",
"Commit together to establish baseline"
]
}
3. 验证新鲜度
检查派生文件是否与源文件同步。 输入:包含 golden-master 元数据的文件路径或目录 输出:过时报告{
"operation": "validate",
"metadata": {
"timestamp": "2026-02-04T12:00:00Z",
"files_scanned": 4,
"relationships_tracked": 2
},
"result": {
"fresh": [
{
"derived": "docs/guides/QUICKSTART.md",
"source": "docs/ARCHITECTURE.md",
"status": "Current (checksums match)"
}
],
"stale": [
{
"derived": "README.md",
"source": "docs/ARCHITECTURE.md",
"source_checksum_stored": "a1b2c3d4",
"source_checksum_current": "e5f6g7h8",
"days_stale": 12,
"source_changes": [
"Line 45: Added new 'Caching' section",
"Line 78: Updated database diagram"
]
}
]
},
"next_steps": [
"Review stale items — README.md needs attention (12 days behind)",
"After updating derived files, run 'refresh' to sync checksums"
]
}
4. 刷新校验和
手动同步派生内容后更新元数据。 输入:派生文件路径(手动更新后) 输出:更新的元数据注释{
"operation": "refresh",
"metadata": {
"timestamp": "2026-02-04T12:00:00Z",
"files_scanned": 1,
"relationships_tracked": 1
},
"result": {
"file": "README.md",
"old_source_checksum": "a1b2c3d4",
"new_source_checksum": "e5f6g7h8",
"updated_comment": ""
},
"next_steps": [
"Replace the golden-master comment in README.md with the updated version",
"Commit with message describing what was synchronized"
]
}
元数据格式
文件内注释(推荐)
源文件:
派生文件:
独立清单(备选)
用于集中追踪:# .golden-master.yaml
version: 1
relationships:
- source: docs/ARCHITECTURE.md
checksum: a1b2c3d4
derived:
- path: README.md
source_checksum: a1b2c3d4
derived_at: 2026-02-04
校验和规范
算法:SHA256,带内容归一化 归一化步骤(哈希前必须执行):
- 行尾统一为 LF(Unix 风格)
- 每行去除末尾空白
- 排除 golden-master 元数据注释:剔除匹配
的内容(非贪婪,单行)
显示:哈希前 8 字符(内部存储完整哈希)
实现:需自定义归一化。标准 sha256sum 无法完成上述步骤。
示例流程:
# Normalize and hash (requires sed + shasum)
cat FILE | \
sed 's/\r$//' | \ # CRLF → LF
sed 's/[[:space:]]$//' | \ # Trim trailing whitespace
sed 's///g' | \ # Strip metadata
shasum -a 256 | \
cut -c1-8 # First 8 chars for display
注意:实现本技能的 AI 代理应以编程方式执行归一化,而非使用 shell。上述流程仅供手动验证。
输出模式
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": ["operation", "metadata", "result", "next_steps"],
"properties": {
"operation": {
"type": "string",
"enum": ["analyze", "establish", "validate", "refresh"]
},
"metadata": {
"type": "object",
"required": ["timestamp", "files_scanned", "relationships_tracked"],
"properties": {
"timestamp": { "type": "string", "format": "date-time" },
"files_scanned": { "type": "integer", "minimum": 0 },
"relationships_tracked": { "type": "integer", "minimum": 0 }
}
},
"result": {
"type": "object",
"description": "Operation-specific result (see Core Operations for each operation's result structure)"
},
"next_steps": {
"type": "array",
"items": { "type": "string" },
"minItems": 1,
"maxItems": 2
},
"error": {
"type": "object",
"required": ["code", "message"],
"properties": {
"code": {
"type": "string",
"enum": ["NO_FILES", "NO_METADATA", "INVALID_PATH", "CHECKSUM_MISMATCH"]
},
"message": { "type": "string" },
"suggestion": { "type": "string" }
}
}
}
}
注意:result 对象结构因操作而异,详见“核心操作”部分各操作的返回字段(如 analyze 返回 relationships[],validate 返回 fresh[] 与 stale[])。
错误处理
| 错误码 | 触发条件 | 消息 | 建议 |
|---|---|---|---|
NO_FILES | 路径下无文件 | "I couldn't find any files at that path." | "Check the path exists and contains files I can read." |
NO_METADATA | 未找到 golden-master 元数据 | "I don't see any golden-master tracking metadata." | "Run 'establish' first to set up tracking relationships." |
INVALID_PATH | 路径穿越或非法字符 | "That path doesn't look right." | "Use relative paths from project root, no '..' allowed." |
CHECKSUM_MISMATCH | 存储的校验和格式非法 | "The checksum in metadata doesn't match expected format." | "Checksums should be 8+ hex characters. Was the file manually edited?" |
术语规则
| 术语 | 用于 | 绝不用于 |
|---|---|---|
| Source | 作为他人真相源的权威文件 | 派生文件 |
| Derived | 基于源文件内容的文件 | 源文件 |
| Stale | 源校验和已变的派生文件 | 无追踪的文件 |
| Fresh | 校验和匹配的派生文件 | 新文件 |
| Tracking | 已建立元数据关系 | 非正式引用 |
相关技能
- principle-synthesizer:从多源合成中识别 Golden Master 候选
- core-refinery:对话式合成,输出 Golden Master 候选
- pbe-extractor:提取可能成为 Golden Master 的原则
必要免责声明
本技能仅识别关系并检测过时状态——不验证派生内容是否准确反映源文件。检测到过时时,请审查源变更并相应更新派生内容。本技能追踪结构,而非语义正确性。
Built by Obviously Not —— 思维工具,非结论。*