TsCarpe
UserAI-native SDLC skills for Claude Code: requirement intake & audit, adversarial review gate, AI test orchestration, decision re-check, release config audit
Categories
Indexed Skills (5)
sdlc-config-review
扫描当前分支相对基线分支（master/main）的 Java 代码 diff，提取三类需要配置中心（Apollo/Nacos）注入的配置项——@Value 单值、@ConfigurationProperties 前缀、任意注解属性中的 ${...} 占位符（如 @FeignClient/@RocketMQMessageListener），产出上线新增 Key 清单（结果表格 + 可复制纯文本块）。Use when 用户要梳理上线配置清单、检查新增配置 Key、准备 Apollo/Nacos 发版配置、提到配置项 diff、@Value、ConfigurationProperties、注解占位符，或说 config-sentinel、config review、Apollo/Nacos key audit、release config checklist。
sdlc-doubt
对刚做出的非平凡技术决策发起对抗式独立复查——把决策剥离结论后交给全���上下文的审查者"找问题"。Use when 影响ER或公共组件的决策回写前、复杂SQL/状态机流转定稿前、提交前对"已全范围检查"断言存疑时、用户说"这个判断我不放心""帮我质疑一下这个方案""doubt-review"。
sdlc-gate
评审关口：技术设计与测试用例定稿后的强制评审关口——4 个全新上下文子代理（3 角色预审 + 1 交叉审查）产出 issue 清单与分歧清单，人工逐条裁决后放行开发/测试执行。Use when 技术设计或测试用例已产出待评审、用户说 评审关口、设计评审、用例预审、交叉审查、review gate、adversarial review、design review、review-gate，或需求梳理确认后设计与用例并行产出完毕。用法：/sdlc-gate <需求名>
sdlc-intent
Digests and health-checks product requirement documents (PRD). Stage 1 produces a structured digest (roles, concepts, feature map, flow diagrams, state machines) to build shared understanding; stage 2 audits the requirement against a six-layer defect taxonomy and produces a graded issue report plus a PM clarification checklist. Use when the user shares a requirement/PRD document (Feishu/wiki link or local file) and wants to understand it, prepare for design, or find problems before development. 触发词：需求文档、需求梳理、需求体检、需求评审、产品需求、帮我理解这个需求、requirement-intake、sdlc-intake、PRD digest、requirement audit.
sdlc-test
AI 测试智能体编排：用例生成 → 静态代码一致性检测 → test 环境浏览器功能测试 → 报告生成。子命令（cases/static/exec/spec/report）独立可重跑，两道人工关卡（用例审核、报告复验）；通过用例可资产化为 Playwright spec，回归轮跑 runner 零 agent token。Use when 用户要求 AI 测试、生成测试用例、执行测试、提测验证、回归测试、生成回归脚本、spec 资产化，或说 ai-test、AI testing、test generation、browser E2E、playwright spec。用法：/sdlc-test cases|static|exec|spec|report <需求名>
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.