openspec-archive

仓库创建 2026年7月28日最近提交 7 小时前SkillHot 收录 1 小时前

▸ 精选理由

关闭循环，保持规范与实际代码基线一致

▸ 风险提示

依赖 OpenSpec/GSD 工具链与项目文件结构

这个 Skill 做什么

在变更已发布后把 deltas 合入活文档并刷新可追溯快照。

把已发布变更的差异合入活文档并刷新可追溯快照，确保下次变更以真实的基线开始。只在发布成功后运行，会同步 STATE.md、更新 openspec/specs 并生成新的追溯快照，防止规格与实际代码脱节造成后续审计误判。它是发布后的收尾步骤，不能用来规避检查或让未通过的变更过关。

▸ 展开 SKILL.md 英文原文

The post-ship closing step — runs OpenSpec's own archive to fold a shipped change's deltas into the living specs, refreshes the final traceability snapshot, and syncs GSD's STATE.md with what actually shipped. Runs only after ship succeeded; archiving is never a way to make a gate pass.

开发编程规范管理归档开发流程通用

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/mshegolev/gsd-openspec-integration/main/capabilities/openspec/skills/openspec-archive/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/mshegolev/gsd-openspec-integration/main/capabilities/openspec/skills/openspec-archive/SKILL.md"

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

## Purpose

Closing the loop so the *next* change starts from an accurate picture of current truth. An unarchived shipped change leaves `openspec/specs/` describing a system that no longer exists, which silently poisons every later drift audit — class 7 (behavior change without spec delta) is only meaningful if the baseline it diffs against is current.

## Invocation conditions

- After `/gsd-ship` has completed successfully — that is, after the `ship:pre` gate passed on `OPENSPEC-VERIFICATION.md` `status: passed` and the ship itself went through.
- Directly, `/openspec-archive <change-id>`, to close out a change shipped before this capability was installed.
- **Never** invoked to clear a bl

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