openspec-drift

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

▸ 精选理由

帮助发现范围蔓延与未记录行为，适合发版前合规检查。

▸ 风险提示

需要访问代码仓库、测试和证据，要求仓库读取权限。

这个 Skill 做什么

审计规范与实现间的漂移，找出代码与规范不一致的情况。

把 OpenSpec、计划、git diff、测试和证据交叉校验，找出规范与实现之间的漂移：规范写了没实现、代码有但没规范等多种偏差。在做严格合规审计、版本回顾或控制范围蔓延时用，能把那些没人留意的隐性变化暴露出来。关键是双向检查——既看是否按规范做，也找出规范没说却被实现的功能，防止 scope creep。

▸ 展开 SKILL.md 英文原文

The Level 6 spec-drift audit — cross-references OpenSpec against GSD plans, git diff, tests, and evidence to find the nine drift classes (requirement without implementation, code without requirement, closed task with no diff, behavior change with no spec delta, and so on). Consumed by openspec-verify for its roll-up and by openspec-audit in strict mode and above.

开发编程漂移审计规范一致性实现追踪通用

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

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

或 curl 直取 SKILL.md

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

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

## Purpose

Every other verification level asks "did we do what the spec said?" This one asks the harder, opposite question too: "is there anything here the spec never said?" Drift is bidirectional, and the direction nobody checks — code with no requirement behind it — is where scope creep and undocumented behavior accumulate.

## Invocation conditions

- Composed by `openspec-audit` in `strict`, `release`, and `forensic` modes.
- Consumed by `openspec-verify` as its Level 6 — that skill reads this one's summary verdict and does **not** reimplement the checks inline.
- Directly, `/openspec-drift`, when a change feels like it has grown beyond its proposal.

## Required inputs

- A change-id,

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