{"id":"e44ed560-eb54-48e9-99a7-e16023275564","version_id":"ec4ff317-df1a-4dca-a436-2b4d58f8511c","reporter":"sdlc-registry-validate","bug_summary":"SDLC registry 校验失败: 8 个 stage skill 缺失","root_cause":"反馈原文\"8 个 stage skill 缺失\"与事实不符:实际只缺 3 个(ci/test/deploy),其余 5 个(requirement/design/code/operate/feedback)状态正常。根因是 registry.json 契约错配:这 3 个 stage 在 SOP.md L458-469 明确被定义为 GitHub Action 形态(sdlc-ci.yml / sdlc-test.yml / sdlc-deploy.yml),\"自动化密集 → GH Action 承载\"是 SOP L471-473 的设计原则;registry.json L10-12 误把它们写成 skill 名,所以 validate.py 才报\"找不到目录\"。报告人 fix_plan 说\"已修复 + 配跨云异地备份\"是误导,这两件事跟本 bug 无关。\n\n验证证据:\n- /home/hq/.claude/skills/sdlc/registry.json L7-14 (错的 stage→skill 映射)\n- /home/hq/.claude/specs/sdlc/SOP.md L458-473 (Workflow 承载对照表)\n- /home/hq/.claude/skills/sdlc-registry-validate/scripts/validate.py L36-51 (校验逻辑)","fix_plan":"推荐方案 A(最小入侵):\n1. 改 registry.json:ci/test/deploy 三个 stage 的 skill 字段置 null,新增并列字段 ci_action / test_action / deploy_action,值分别为 sdlc-ci.yml / sdlc-test.yml / sdlc-deploy.yml\n2. 改 sdlc-registry-validate/scripts/validate.py:对 skill=null + 存在 _action 字段的 stage,改为检查对应 yaml 文件存在性,缺失时仍报 severity=medium\n3. 改 ~/.claude/skills/sdlc/SKILL.md (总入口启动逻辑):遇到 null + action 字段显示\"GH Action\"标识而非\"待接入\"\n\n不推荐:\n- 方案 B(把 workflow 落到 skills 命名空间):与 skill 概念耦合度更高\n- 方案 C(从 registry 删 ci/test/deploy):破坏 /sdlc 8 阶段菜单,违反 SOP L460","severity":"medium","status":"fixed","decision":"reassess_form","reused_in_projects":[],"decided_at":"2026-06-22T02:36:37.700361","created_at":"2026-06-21T17:55:18.833984","requirement_id":null}