@hupan56/wlkj 2.2.4 → 2.2.6

package/templates/qoder/skills/test-generator/SKILL.md

@@ -1,72 +1,72 @@
----
-name: test-generator
-description: "从已实现代码和 Spec 自动生成单元测试。Auto-generate unit tests from implemented code and Spec. 用户说'写单元测试''补测试''覆盖一下''写个test'时触发。需用户确认（DANGEROUS）。"
-trigger: "代码实现完成后；用户说'写测试''补单测''生成test''/wl-test'"
----
-
-# Test Generator
-
-按团队规范，基于已实现代码和 Spec 生成单元测试。
-
-> ⚠️ 这是 DANGEROUS 操作（会写源码）。执行前必须向用户确认。
-
-## ⚙️ 自取上下文（Quest / QoderWork 无 hook 注入，必须自读）
-
-- `.qoder/.developer` — 当前开发者
-- `.qoder/.current-task` — 当前任务
-- Spec 文件：`workspace/specs/REQ-{ID}-*.spec.md` 或 `workspace/tasks/{task-id}/spec.md`
-- 已实现代码：用 search_index.py 定位
-  ```bash
-  python .qoder/scripts/search_index.py <类名或模块关键词>
-  ```
-
-## Step 1: 定位待测代码
-
-```bash
-ls workspace/specs/REQ-{ID}-*.md  # Spec 文件（测试用例映射源）
-ls data/code/                     # 已实现代码库
-```
-
-把 Spec 匹配到对应的实现文件。
-
-## Step 2: 读取上下文
-
-1. **实现代码**（必需）：当前需求相关的 `data/code/` 文件
-2. **Spec 文件**（推荐）：测试用例映射来源
-3. **现有测试代码**（推荐）：用 search_index.py 找同类 Test 类，照着写
-   ```bash
-   python .qoder/scripts/search_index.py Test
-   ```
-
-## Step 3: 生成测试
-
-参照现有 Test 类的写法（命名、断言库、Mock 方式），不另起炉灶：
-
-### Service 层测试
-- 每个公开方法组一个测试类
-- Mock 所有外部依赖（Mapper、外部 Service、Redis 等）
-- 覆盖：正常路径、错误路径、边界条件
-
-### Controller 层测试
-- MockMvc 测端点
-- 校验参数校验
-- 校验返回格式
-
-### 测试方法约定
-- Given-When-Then 模式
-- `@DisplayName` 中文描述
-- 断言用 AssertJ（若现有代码用 JUnit 断言则跟随）
-- 测试数据用 Builder 模式
-
-## Step 4: 输出
-
-- 路径：`tests/{package-path}/{ClassName}Test.java`（跟随现有 test 目录结构）
-- 命名：`{TestedClassName}Test.java`
-- 每个测试方法独立（无执行顺序依赖）
-
-## 测试原则
-
-1. 正常路径 100%，错误路径 100%
-2. 核心业务边界条件全覆盖
-3. 无外部系统依赖（全 Mock）
+---
+name: test-generator
+description: "从已实现代码和 Spec 自动生成单元测试。Auto-generate unit tests from implemented code and Spec. 用户说'写单元测试''补测试''覆盖一下''写个test'时触发。需用户确认（DANGEROUS）。"
+trigger: "代码实现完成后；用户说'写测试''补单测''生成test''/wl-test'"
+---
+
+# Test Generator
+
+按团队规范，基于已实现代码和 Spec 生成单元测试。
+
+> ⚠️ 这是 DANGEROUS 操作（会写源码）。执行前必须向用户确认。
+
+## ⚙️ 自取上下文（Quest / QoderWork 无 hook 注入，必须自读）
+
+- `.qoder/.developer` — 当前开发者
+- `.qoder/.current-task` — 当前任务
+- Spec 文件：`workspace/specs/REQ-{ID}-*.spec.md` 或 `workspace/tasks/{task-id}/spec.md`
+- 已实现代码：用 search_index.py 定位
+  ```bash
+  python .qoder/scripts/search_index.py <类名或模块关键词>
+  ```
+
+## Step 1: 定位待测代码
+
+```bash
+ls workspace/specs/REQ-{ID}-*.md  # Spec 文件（测试用例映射源）
+ls data/code/                     # 已实现代码库
+```
+
+把 Spec 匹配到对应的实现文件。
+
+## Step 2: 读取上下文
+
+1. **实现代码**（必需）：当前需求相关的 `data/code/` 文件
+2. **Spec 文件**（推荐）：测试用例映射来源
+3. **现有测试代码**（推荐）：用 search_index.py 找同类 Test 类，照着写
+   ```bash
+   python .qoder/scripts/search_index.py Test
+   ```
+
+## Step 3: 生成测试
+
+参照现有 Test 类的写法（命名、断言库、Mock 方式），不另起炉灶：
+
+### Service 层测试
+- 每个公开方法组一个测试类
+- Mock 所有外部依赖（Mapper、外部 Service、Redis 等）
+- 覆盖：正常路径、错误路径、边界条件
+
+### Controller 层测试
+- MockMvc 测端点
+- 校验参数校验
+- 校验返回格式
+
+### 测试方法约定
+- Given-When-Then 模式
+- `@DisplayName` 中文描述
+- 断言用 AssertJ（若现有代码用 JUnit 断言则跟随）
+- 测试数据用 Builder 模式
+
+## Step 4: 输出
+
+- 路径：`tests/{package-path}/{ClassName}Test.java`（跟随现有 test 目录结构）
+- 命名：`{TestedClassName}Test.java`
+- 每个测试方法独立（无执行顺序依赖）
+
+## 测试原则
+
+1. 正常路径 100%，错误路径 100%
+2. 核心业务边界条件全覆盖
+3. 无外部系统依赖（全 Mock）
 4. 测试方法之间无相互依赖

package/templates/root/AGENTS.md

@@ -1,182 +1,182 @@
-# QODER Pipeline
-
-## ⚠️ CRITICAL RULE #1: ALWAYS ASK PLATFORM FIRST
-
-**When user asks for PRD or prototype, you MUST ask this question FIRST:**
-
-```
-这个需求是针对哪个平台？
-
-1. **Web 管理端** (fywl-ui) - Ant Design Vue + VxeGrid 风格
-2. **APP 移动端** (Carmg-H5) - Vant 风格  
-3. **两端都要**
-
-请选择 (1/2/3):
-```
-
-**DO NOT skip this question. DO NOT auto-detect. ALWAYS ASK.**
-**Wait for user answer before doing ANYTHING else.**
-
----
-
-## CRITICAL RULE #2: Use /wl-search to find code
-
-When user asks about code, business, API, feature:
-1. **ALWAYS** use `/wl-search <keyword>` command first
-2. Then read only the specific files returned
-3. **NEVER** grep the entire codebase directly
-
-Examples:
-- "考勤代码在哪" -> /wl-search attendance
-- "保险定时任务" -> /wl-search insurance
-- "薪资API" -> /wl-search --api salary
-
-## CRITICAL RULE #2.5: 自然语言 → 技能 路由（Quest / QoderWork 入口）
-
-Quest 与 QoderWork 没有斜杠命令，AI 必须按下表把用户自然语言映射到
-`.qoder/skills/` 下的技能（Qoder IDE 编辑器与 CLI 用 `/wl-*` 命令，同样适用）：
-
-| 用户说什么 | 触发 skill |
-|------------|-----------|
-| "写个需求""生成PRD""做个原型" | prd-generator + prototype-generator |
-| "查一下""代码在哪""搜保险""考勤API" | wl-search |
-| "建任务""排优先级""任务做完了" | wl-task |
-| "项目怎么样""进度""健康度" | wl-status |
-| "写日报""周报""我干了啥" | wl-report |
-| "用户反馈""数据怎么样" | wl-insight |
-| "生成规格""写spec" | spec-generator |
-| "开始写代码""按规格实现" | spec-coder |
-| "写单元测试" | test-generator |
-| "评审PRD" | prd-review |
-| "提交代码""commit""推上去" | wl-commit |
-| "初始化""换开发者""环境检查" | wl-init |
-
-找不到明确匹配 → 先问用户意图，不要乱跑。
-注意区分："同步/保存产出" = team_sync（push）；"提交/commit 代码" = wl-commit。
-
-## CRITICAL RULE #3: User NEVER touches git
-
-PMs on this team do not know git. ALL git operations are invisible:
-- After any publish/save action (/wl-prd publish, /wl-task create/finish,
-  /wl-report save), run: `python .qoder/scripts/team_sync.py push`
-- To get teammates' latest work: `python .qoder/scripts/team_sync.py pull`
-- If team_sync prints SYNC_CONFLICT, YOU (the AI) resolve the conflict
-  yourself (it tells you the commands). NEVER ask the user to run git.
-- When the user says 同步/保存/提交 in natural language -> team_sync, not raw git.
-
-## Platform Filtering
-
-After user selects platform, use it for search:
-
-```bash
-# Search by platform
-/wl-search 保险 --platform web      # Only fywl-ui (PC)
-/wl-search 保险 --platform app      # Only Carmg-H5 (Mobile)
-/wl-search 保险                       # Both platforms
-
-# Platform shortcuts
-web/pc/管理端 -> fywl-ui
-app/mobile/h5/移动端 -> Carmg-H5
-```
-
-## 11 Commands (All prefixed /wl-)
-
-### Pipeline Core
-| Command | Auto | Purpose |
-|---------|------|---------|
-| `/wl-init` | YES | Register/switch developer identity |
-| `/wl-prd` | YES | Generate PRD (ASKS platform first!) |
-| `/wl-spec` | YES | Generate technical Spec from PRD |
-| `/wl-code` | NO | Code implementation (needs confirm) |
-| `/wl-commit` | NO | Git commit + push + sync (needs confirm) |
-
-### Product Management
-| Command | Auto | Purpose |
-|---------|------|---------|
-| `/wl-search` | YES | Search code index (supports Chinese, platform filtering) |
-| `/wl-task` | YES | Task management + RICE prioritization |
-| `/wl-status` | YES | Project status + roadmap + health |
-| `/wl-insight` | YES | Feedback analysis + metrics review |
-
-### Reporting
-| Command | Auto | Purpose |
-|---------|------|---------|
-| `/wl-report` | YES | Generate daily or weekly work report |
-| `/wl-test` | NO | Generate unit tests (needs confirm) |
-
-## Knowledge Index
-
-3 projects: Carmg-H5(1378 files), fywl-ics(8973 files, 3903 APIs), fywl-ui(3270 files)
-Search: /wl-search <keyword> returns compact results (~200 bytes)
-Weekly sync: python .qoder/scripts/git_sync.py
-
-### Style Index (Prototype Reference)
-UI patterns from Vue files: Tables(718), Forms(301), Detail(129), Dashboard(90)
-Top components: Space(583), Modal(270), Select(172), Input(134)
-Form components: Input(2262), Select(1049), ApiSelect(725), DatePicker(265)
-Field map: 2383 entries
-
-Style search:
-  python .qoder/scripts/search_index.py --style table/form/modal/dashboard
-  python .qoder/scripts/search_index.py --field <field_name>
-  python .qoder/scripts/search_index.py --components
-  python .qoder/scripts/search_index.py --vben    # Vben Admin CSS variables
-
-Prototype templates:
-  .qoder/templates/prototype-web.html   # Web管理端 (Vben Admin + Ant Design)
-  .qoder/templates/prototype-app.html   # APP移动端 (Vant)
-
-Prototype output: workspace/members/{dev}/drafts/prototype-{feature}.html
-Style priority: Code > PDF > Default
-
-## Workflow
-
-/wl-init -> /wl-prd (ASK PLATFORM!) -> /wl-task -> /wl-spec -> /wl-code -> /wl-test -> /wl-commit -> /wl-report
-
-## Cross-platform & Qoder Product Family Compatibility
-
-This pipeline works on Windows + macOS, across the whole Qoder family.
-Each product loads rules from a different carrier — keep them in sync:
-
-| 产品/模式 | 规则载体 | 命令载体 |
-|-----------|---------|---------|
-| Qoder IDE 默认编辑器 | .qoder/rules/wl-pipeline.md (always_on) | .qoder/commands/wl-*.md |
-| Qoder Quest 模式 | .qoder/rules/ + .qoder/skills/ + .qoder/agents/ | 自然语言 -> skills |
-| Qoder CLI (qodercli) | 本文件 AGENTS.md | 自然语言 -> scripts |
-| QoderWork 桌面 Agent | 安装 .qoder/skills/ 下的技能 | 自然语言 -> skills |
-| Claude Code 等其他工具 | 本文件 AGENTS.md | .qoder/commands/wl-*.md |
-
-- THE rule file: `.qoder/rules/wl-pipeline.md` — 修改流程规则时同步更新它和本文件
-- Quest 修改 agents/skills 后需重启 Quest 窗口/新建对话才能生效（Qoder 已知限制）
-- **Repo Wiki** (`.qoder/repowiki/`, Qoder IDE 生成): 存在则作为模块级知识源,
-  写 PRD 前优先查相关模块页；可提交 git 团队共享。索引管"定位", Wiki 管"理解"。
-- All scripts are pure Python 3 + git, path-autodetecting (no hardcoded
-  drive letters). Invoke as `python` (Windows) or `python3` (macOS).
-- Weekly update: Windows -> scripts/setup_weekly_cron.bat,
-  macOS/Linux -> scripts/setup_weekly_cron.sh. Only ONE machine per team
-  needs this; everyone else gets the graph via /wl-init's auto pull.
-- Environment problems of any kind -> run:
-  `python .qoder/scripts/init_doctor.py` (add --fix to auto-repair).
-
-## Fast Path: one call to get all context
-
-`python .qoder/scripts/context_pack.py <业务词> --platform <web|app>` returns
-code files + page examples + field specs + PRDs + APIs + style/icon pointers
-in ONE call. Use it FIRST; fall back to search_index.py for drill-down.
-
-## Icons: NEVER emoji
-
-Prototypes use the projects' real icon systems (data/index/icon-reference.json):
-Web = Ant Design inline SVG, APP = Vant font icons. Emoji in a prototype = FAIL.
-
-## Quality Gate (EVA)
-
-Before publishing any PRD: `python .qoder/scripts/eval_prd.py <prd> [prototype]`
-must PASS (>=80%). Metrics definition: data/docs/constitution/eva-metrics.md
-
-## Permission Model
-
-| Level | Commands | Auto |
-|-------|---------|------|
-| SAFE | /wl-init, /wl-prd, /wl-search, /wl-task, /wl-spec, /wl-status, /wl-insight, /wl-report | YES |
-| DANGEROUS | /wl-code, /wl-test, /wl-commit | NO |
+# QODER Pipeline
+
+## ⚠️ CRITICAL RULE #1: ALWAYS ASK PLATFORM FIRST
+
+**When user asks for PRD or prototype, you MUST ask this question FIRST:**
+
+```
+这个需求是针对哪个平台？
+
+1. **Web 管理端** (fywl-ui) - Ant Design Vue + VxeGrid 风格
+2. **APP 移动端** (Carmg-H5) - Vant 风格  
+3. **两端都要**
+
+请选择 (1/2/3):
+```
+
+**DO NOT skip this question. DO NOT auto-detect. ALWAYS ASK.**
+**Wait for user answer before doing ANYTHING else.**
+
+---
+
+## CRITICAL RULE #2: Use /wl-search to find code
+
+When user asks about code, business, API, feature:
+1. **ALWAYS** use `/wl-search <keyword>` command first
+2. Then read only the specific files returned
+3. **NEVER** grep the entire codebase directly
+
+Examples:
+- "考勤代码在哪" -> /wl-search attendance
+- "保险定时任务" -> /wl-search insurance
+- "薪资API" -> /wl-search --api salary
+
+## CRITICAL RULE #2.5: 自然语言 → 技能 路由（Quest / QoderWork 入口）
+
+Quest 与 QoderWork 没有斜杠命令，AI 必须按下表把用户自然语言映射到
+`.qoder/skills/` 下的技能（Qoder IDE 编辑器与 CLI 用 `/wl-*` 命令，同样适用）：
+
+| 用户说什么 | 触发 skill |
+|------------|-----------|
+| "写个需求""生成PRD""做个原型" | prd-generator + prototype-generator |
+| "查一下""代码在哪""搜保险""考勤API" | wl-search |
+| "建任务""排优先级""任务做完了" | wl-task |
+| "项目怎么样""进度""健康度" | wl-status |
+| "写日报""周报""我干了啥" | wl-report |
+| "用户反馈""数据怎么样" | wl-insight |
+| "生成规格""写spec" | spec-generator |
+| "开始写代码""按规格实现" | spec-coder |
+| "写单元测试" | test-generator |
+| "评审PRD" | prd-review |
+| "提交代码""commit""推上去" | wl-commit |
+| "初始化""换开发者""环境检查" | wl-init |
+
+找不到明确匹配 → 先问用户意图，不要乱跑。
+注意区分："同步/保存产出" = team_sync（push）；"提交/commit 代码" = wl-commit。
+
+## CRITICAL RULE #3: User NEVER touches git
+
+PMs on this team do not know git. ALL git operations are invisible:
+- After any publish/save action (/wl-prd publish, /wl-task create/finish,
+  /wl-report save), run: `python .qoder/scripts/team_sync.py push`
+- To get teammates' latest work: `python .qoder/scripts/team_sync.py pull`
+- If team_sync prints SYNC_CONFLICT, YOU (the AI) resolve the conflict
+  yourself (it tells you the commands). NEVER ask the user to run git.
+- When the user says 同步/保存/提交 in natural language -> team_sync, not raw git.
+
+## Platform Filtering
+
+After user selects platform, use it for search:
+
+```bash
+# Search by platform
+/wl-search 保险 --platform web      # Only fywl-ui (PC)
+/wl-search 保险 --platform app      # Only Carmg-H5 (Mobile)
+/wl-search 保险                       # Both platforms
+
+# Platform shortcuts
+web/pc/管理端 -> fywl-ui
+app/mobile/h5/移动端 -> Carmg-H5
+```
+
+## 11 Commands (All prefixed /wl-)
+
+### Pipeline Core
+| Command | Auto | Purpose |
+|---------|------|---------|
+| `/wl-init` | YES | Register/switch developer identity |
+| `/wl-prd` | YES | Generate PRD (ASKS platform first!) |
+| `/wl-spec` | YES | Generate technical Spec from PRD |
+| `/wl-code` | NO | Code implementation (needs confirm) |
+| `/wl-commit` | NO | Git commit + push + sync (needs confirm) |
+
+### Product Management
+| Command | Auto | Purpose |
+|---------|------|---------|
+| `/wl-search` | YES | Search code index (supports Chinese, platform filtering) |
+| `/wl-task` | YES | Task management + RICE prioritization |
+| `/wl-status` | YES | Project status + roadmap + health |
+| `/wl-insight` | YES | Feedback analysis + metrics review |
+
+### Reporting
+| Command | Auto | Purpose |
+|---------|------|---------|
+| `/wl-report` | YES | Generate daily or weekly work report |
+| `/wl-test` | NO | Generate unit tests (needs confirm) |
+
+## Knowledge Index
+
+3 projects: Carmg-H5(1378 files), fywl-ics(8973 files, 3903 APIs), fywl-ui(3270 files)
+Search: /wl-search <keyword> returns compact results (~200 bytes)
+Weekly sync: python .qoder/scripts/git_sync.py
+
+### Style Index (Prototype Reference)
+UI patterns from Vue files: Tables(718), Forms(301), Detail(129), Dashboard(90)
+Top components: Space(583), Modal(270), Select(172), Input(134)
+Form components: Input(2262), Select(1049), ApiSelect(725), DatePicker(265)
+Field map: 2383 entries
+
+Style search:
+  python .qoder/scripts/search_index.py --style table/form/modal/dashboard
+  python .qoder/scripts/search_index.py --field <field_name>
+  python .qoder/scripts/search_index.py --components
+  python .qoder/scripts/search_index.py --vben    # Vben Admin CSS variables
+
+Prototype templates:
+  .qoder/templates/prototype-web.html   # Web管理端 (Vben Admin + Ant Design)
+  .qoder/templates/prototype-app.html   # APP移动端 (Vant)
+
+Prototype output: workspace/members/{dev}/drafts/prototype-{feature}.html
+Style priority: Code > PDF > Default
+
+## Workflow
+
+/wl-init -> /wl-prd (ASK PLATFORM!) -> /wl-task -> /wl-spec -> /wl-code -> /wl-test -> /wl-commit -> /wl-report
+
+## Cross-platform & Qoder Product Family Compatibility
+
+This pipeline works on Windows + macOS, across the whole Qoder family.
+Each product loads rules from a different carrier — keep them in sync:
+
+| 产品/模式 | 规则载体 | 命令载体 |
+|-----------|---------|---------|
+| Qoder IDE 默认编辑器 | .qoder/rules/wl-pipeline.md (always_on) | .qoder/commands/wl-*.md |
+| Qoder Quest 模式 | .qoder/rules/ + .qoder/skills/ + .qoder/agents/ | 自然语言 -> skills |
+| Qoder CLI (qodercli) | 本文件 AGENTS.md | 自然语言 -> scripts |
+| QoderWork 桌面 Agent | 安装 .qoder/skills/ 下的技能 | 自然语言 -> skills |
+| Claude Code 等其他工具 | 本文件 AGENTS.md | .qoder/commands/wl-*.md |
+
+- THE rule file: `.qoder/rules/wl-pipeline.md` — 修改流程规则时同步更新它和本文件
+- Quest 修改 agents/skills 后需重启 Quest 窗口/新建对话才能生效（Qoder 已知限制）
+- **Repo Wiki** (`.qoder/repowiki/`, Qoder IDE 生成): 存在则作为模块级知识源,
+  写 PRD 前优先查相关模块页；可提交 git 团队共享。索引管"定位", Wiki 管"理解"。
+- All scripts are pure Python 3 + git, path-autodetecting (no hardcoded
+  drive letters). Invoke as `python` (Windows) or `python3` (macOS).
+- Weekly update: Windows -> scripts/setup_weekly_cron.bat,
+  macOS/Linux -> scripts/setup_weekly_cron.sh. Only ONE machine per team
+  needs this; everyone else gets the graph via /wl-init's auto pull.
+- Environment problems of any kind -> run:
+  `python .qoder/scripts/init_doctor.py` (add --fix to auto-repair).
+
+## Fast Path: one call to get all context
+
+`python .qoder/scripts/context_pack.py <业务词> --platform <web|app>` returns
+code files + page examples + field specs + PRDs + APIs + style/icon pointers
+in ONE call. Use it FIRST; fall back to search_index.py for drill-down.
+
+## Icons: NEVER emoji
+
+Prototypes use the projects' real icon systems (data/index/icon-reference.json):
+Web = Ant Design inline SVG, APP = Vant font icons. Emoji in a prototype = FAIL.
+
+## Quality Gate (EVA)
+
+Before publishing any PRD: `python .qoder/scripts/eval_prd.py <prd> [prototype]`
+must PASS (>=80%). Metrics definition: data/docs/constitution/eva-metrics.md
+
+## Permission Model
+
+| Level | Commands | Auto |
+|-------|---------|------|
+| SAFE | /wl-init, /wl-prd, /wl-search, /wl-task, /wl-spec, /wl-status, /wl-insight, /wl-report | YES |
+| DANGEROUS | /wl-code, /wl-test, /wl-commit | NO |