@fitlab-ai/agent-infra 0.3.1 → 0.4.0

package/templates/.agents/skills/plan-task/SKILL.zh-CN.md

@@ -18,7 +18,7 @@ description: >
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+- `.agents/workspace/active/{task-id}/task.md` - 任务文件
 - 至少一个分析产物：`analysis.md` 或 `analysis-r{N}.md`
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
@@ -27,7 +27,7 @@ description: >
 
 ### 2. 确定方案轮次
 
-扫描 `.agent-workspace/active/{task-id}/` 目录中的方案产物文件：
+扫描 `.agents/workspace/active/{task-id}/` 目录中的方案产物文件：
 - 如果不存在 `plan.md` 且不存在 `plan-r*.md` → 本轮为第 1 轮，产出 `plan.md`
 - 如果存在 `plan.md` 且不存在 `plan-r*.md` → 本轮为第 2 轮，产出 `plan-r2.md`
 - 如果存在 `plan-r{N}.md` → 本轮为第 N+1 轮，产出 `plan-r{N+1}.md`
@@ -75,7 +75,7 @@ description: >
 
 ### 6. 输出计划文档
 
-创建 `.agent-workspace/active/{task-id}/{plan-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{plan-artifact}`。
 
 ### 7. 更新任务状态
 
@@ -85,7 +85,7 @@ description: >
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：technical-design
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
@@ -113,7 +113,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 预估复杂度：{评估}
 
 产出文件：
-- 技术方案：.agent-workspace/active/{task-id}/{plan-artifact}
+- 技术方案：.agents/workspace/active/{task-id}/{plan-artifact}
 
 重要：人工审查检查点。
 请在继续实现之前审查技术方案。
@@ -198,7 +198,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 - [ ] 阅读并理解了需求分析
 - [ ] 考虑了备选方案
-- [ ] 创建了计划文档 `.agent-workspace/active/{task-id}/{plan-artifact}`
+- [ ] 创建了计划文档 `.agents/workspace/active/{task-id}/{plan-artifact}`
 - [ ] 更新了 task.md 中的 `current_step` 为 technical-design
 - [ ] 更新了 task.md 中的 `updated_at` 为当前时间
 - [ ] 在 task.md 中记录了 `{plan-artifact}` 为已完成产物

package/templates/.agents/skills/refine-task/SKILL.md

@@ -20,7 +20,7 @@ description: >
 ### 1. Verify Prerequisites
 
 Check required files:
-- `.agent-workspace/active/{task-id}/task.md` - Task file
+- `.agents/workspace/active/{task-id}/task.md` - Task file
 - At least one review artifact: `review.md` or `review-r{N}.md`
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, for example `TASK-20260306-143022`
@@ -86,7 +86,7 @@ Ensure all tests still pass after the fixes.
 
 ### 6. Create Refinement Report
 
-Create `.agent-workspace/active/{task-id}/{refinement-artifact}`.
+Create `.agents/workspace/active/{task-id}/{refinement-artifact}`.
 
 ### 7. Update Task Status
 
@@ -96,7 +96,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: refinement
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}

package/templates/.agents/skills/refine-task/SKILL.zh-CN.md

@@ -18,7 +18,7 @@ description: >
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+- `.agents/workspace/active/{task-id}/task.md` - 任务文件
 - 至少一个审查产物：`review.md` 或 `review-r{N}.md`
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
@@ -84,7 +84,7 @@ description: >
 
 ### 6. 创建修复报告
 
-创建 `.agent-workspace/active/{task-id}/{refinement-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{refinement-artifact}`。
 
 ### 7. 更新任务状态
 
@@ -94,7 +94,7 @@ description: >
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：refinement
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}

package/templates/.agents/skills/release/SKILL.md

@@ -31,7 +31,26 @@ git status --short
 
 If there are uncommitted changes, error: "Workspace has uncommitted changes. Please commit or stash first."
 
-### Step 3: Update Version References
+### Step 3: Pre-release Verification
+
+<!-- TODO: Replace with your project's pre-release verification steps -->
+
+Run any checks that must pass before preparing a release:
+
+```bash
+git branch --show-current
+# TODO: Replace with your project's test/build verification commands
+```
+
+Verification guidance:
+- Confirm the release is being prepared from the correct branch for your project
+- Run the full validation commands required by your release process
+
+Handling rules:
+- If the current branch is unexpected, print a warning or exit based on your policy
+- If any verification command fails, stop the release process and fix the issue first
+
+### Step 4: Update Version References
 
 <!-- TODO: Replace with your project's version update steps -->
 
@@ -45,6 +64,7 @@ Search for version references in project files and update them:
 
 **Common files to update**:
 - `package.json` (Node.js)
+- `package-lock.json` (Node.js; run `npm install --package-lock-only` after updating `package.json`)
 - `pom.xml` (Maven)
 - `setup.py` / `pyproject.toml` (Python)
 - `version.go` (Go)
@@ -52,22 +72,39 @@ Search for version references in project files and update them:
 - `SECURITY.md` / `SECURITY.zh-CN.md` (supported version table)
 
 **Exclude from version replacement**:
-- `.agents/`, `.agent-workspace/`, `.claude/`, `.codex/`, `.gemini/`, `.opencode/` (AI tool configs)
+- `.agents/`, `.agents/workspace/`, `.claude/`, `.codex/`, `.gemini/`, `.opencode/` (AI tool configs)
+
+If the project uses `package-lock.json`, run `npm install --package-lock-only` after updating `package.json` so the lockfile version stays in sync.
+
+### Step 5: Rebuild Artifacts
 
-### Step 4: Create Release Commit
+<!-- TODO: Replace with your project's artifact rebuild steps -->
+
+If version updates affect generated files, embedded metadata, or bundled assets, rebuild them now:
+
+```bash
+# TODO: Replace with your project's rebuild command(s)
+```
+
+Execution guidance:
+- Run this after updating version references so generated artifacts pick up the new version
+- If your project has no generated artifacts, document that explicitly in the project-specific skill
+- If the rebuild fails, stop the release process and fix the build first
+
+### Step 6: Create Release Commit
 
 ```bash
 git add -A
 git commit -m "chore: release v{version}"
 ```
 
-### Step 5: Create Git Tag
+### Step 7: Create Git Tag
 
 ```bash
 git tag v{version}
 ```
 
-### Step 6: Manage Milestones
+### Step 8: Manage Milestones
 
 Close the milestone for the released version when it exists, and create the missing planning milestones for the next cycle.
 
@@ -84,7 +121,7 @@ The script is responsible for:
 - When `PATCH=0`, also ensuring `{MAJOR}.{MINOR+1}.0` and `{MAJOR}.{MINOR+1}.x`
 - Printing a milestone summary with the released milestone action and new milestone count
 
-### Step 7: Output Summary
+### Step 9: Output Summary
 
 > **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
 
@@ -100,12 +137,12 @@ Files updated: {count}
 
 Next steps (manual):
 
-1. Push tag:
-   git push origin v{version}
-
-2. Push branch:
+1. Push branch:
    git push origin {current-branch}
 
+2. Push tag:
+   git push origin v{version}
+
 3. (Optional) Generate release notes:
    - Claude Code / OpenCode: /create-release-note {version}
    - Gemini CLI: /{{project}}:create-release-note {version}
@@ -130,13 +167,17 @@ git checkout -- .
 
 1. **Clean workspace required**: Must have no uncommitted changes
 2. **No auto-push**: All operations are local only; user pushes manually
-3. **No build verification**: Run the test skill before releasing to verify
-4. **Version replacement scope**: Search determines which files to update; exclude AI tool directories
-5. **Adapt to your project**: The version update steps above are generic; customize for your project's versioning scheme
-6. **Milestone coordination**: Releases should create the next planning milestones automatically; initialize the taxonomy first with `init-milestones` when needed
+3. **Pre-release verification**: Replace the Step 3 TODOs with the branch, test, and validation commands your release process requires
+4. **Generated artifacts**: Replace the Step 5 TODOs when version changes affect generated files, bundled assets, or embedded metadata
+5. **Release automation**: If pushing a tag triggers CI/CD or package publishing, confirm the required credentials and pipeline settings first
+6. **Version replacement scope**: Search determines which files to update; exclude AI tool directories
+7. **Adapt to your project**: The version update and rebuild steps above are generic; customize them for your project's versioning scheme
+8. **Milestone coordination**: Releases should create the next planning milestones automatically; initialize the taxonomy first with `init-milestones` when needed
 
 ## Error Handling
 
 - Invalid version format: Prompt correct format and exit
 - Dirty workspace: Prompt to commit or stash
+- Verification failure: Display the failing check and stop the release
+- Artifact rebuild failure: Display the build error and stop the release
 - Git operation failure: Display error and provide rollback instructions

package/templates/.agents/skills/release/SKILL.zh-CN.md

@@ -30,7 +30,26 @@ git status --short
 
 如果有未提交的变更，报错："Workspace has uncommitted changes. Please commit or stash first."
 
-### 步骤 3：更新版本引用
+### 步骤 3：发布前验证
+
+<!-- TODO: 替换为你的项目发布前验证步骤 -->
+
+运行所有在准备发布前必须通过的检查：
+
+```bash
+git branch --show-current
+# TODO: 替换为你的项目测试/构建验证命令
+```
+
+验证要求：
+- 确认发布使用的是项目规定的分支
+- 运行你的发布流程要求的完整校验命令
+
+处理规则：
+- 如果当前分支不符合预期，按项目策略输出警告或直接退出
+- 如果任何验证命令失败，停止发布流程并先修复问题
+
+### 步骤 4：更新版本引用
 
 <!-- TODO: 替换为你的项目版本更新步骤 -->
 
@@ -44,6 +63,7 @@ git status --short
 
 **常见需要更新的文件**：
 - `package.json`（Node.js）
+- `package-lock.json`（Node.js；更新 `package.json` 后运行 `npm install --package-lock-only` 同步锁文件）
 - `pom.xml`（Maven）
 - `setup.py` / `pyproject.toml`（Python）
 - `version.go`（Go）
@@ -51,22 +71,39 @@ git status --short
 - `SECURITY.md` / `SECURITY.zh-CN.md`（支持版本表格）
 
 **排除以下目录的版本替换**：
-- `.agents/`、`.agent-workspace/`、`.claude/`、`.codex/`、`.gemini/`、`.opencode/`（AI 工具配置）
+- `.agents/`、`.agents/workspace/`、`.claude/`、`.codex/`、`.gemini/`、`.opencode/`（AI 工具配置）
+
+如果项目使用 `package-lock.json`，在更新 `package.json` 后运行 `npm install --package-lock-only`，确保锁文件中的版本号保持同步。
+
+### 步骤 5：重新生成构建产物
 
-### 步骤 4：创建发布提交
+<!-- TODO: 替换为你的项目产物重建步骤 -->
+
+如果版本更新会影响生成文件、内嵌元数据或打包产物，现在重新生成它们：
+
+```bash
+# TODO: 替换为你的项目构建/重建命令
+```
+
+执行要求：
+- 在更新版本引用后运行，确保生成产物使用最新版本号
+- 如果项目没有生成产物，请在项目特化版本中明确说明
+- 如果重建失败，停止发布流程并先修复构建问题
+
+### 步骤 6：创建发布提交
 
 ```bash
 git add -A
 git commit -m "chore: release v{version}"
 ```
 
-### 步骤 5：创建 Git 标签
+### 步骤 7：创建 Git 标签
 
 ```bash
 git tag v{version}
 ```
 
-### 步骤 6：管理里程碑
+### 步骤 8：管理里程碑
 
 为已发布版本关闭对应版本里程碑，并为下一轮创建缺失的规划里程碑。
 
@@ -83,7 +120,7 @@ bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PAT
 - 当 `PATCH=0` 时，同时确保 `{MAJOR}.{MINOR+1}.0` 与 `{MAJOR}.{MINOR+1}.x`
 - 输出包含已发布里程碑动作和新建数量的汇总
 
-### 步骤 7：输出摘要
+### 步骤 9：输出摘要
 
 > **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
 
@@ -99,12 +136,12 @@ bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PAT
 
 下一步（手动执行）：
 
-1. 推送标签：
-   git push origin v{version}
-
-2. 推送分支：
+1. 推送分支：
    git push origin {current-branch}
 
+2. 推送标签：
+   git push origin v{version}
+
 3.（可选）生成发布说明：
    - Claude Code / OpenCode：/create-release-note {version}
    - Gemini CLI：/{{project}}:create-release-note {version}
@@ -129,13 +166,17 @@ git checkout -- .
 
 1. **需要干净的工作区**：必须没有未提交的变更
 2. **不自动推送**：所有操作仅在本地执行；用户手动推送
-3. **不验证构建**：发布前执行 test 技能进行验证
-4. **版本替换范围**：通过搜索确定需要更新哪些文件；排除 AI 工具目录
-5. **适配你的项目**：以上版本更新步骤是通用的；请根据你的项目版本方案进行定制
-6. **里程碑联动**：发布时自动创建下一轮里程碑；如果里程碑体系未初始化，建议先运行 `init-milestones`
+3. **发布前验证**：将步骤 3 的 TODO 替换为你的项目所需的分支、测试和验证命令
+4. **生成产物**：如果版本变化会影响生成文件、打包产物或内嵌元数据，需要将步骤 5 的 TODO 替换为实际命令
+5. **发布自动化**：如果推送标签会触发 CI/CD 或包发布，请先确认所需凭据和流水线配置
+6. **版本替换范围**：通过搜索确定需要更新哪些文件；排除 AI 工具目录
+7. **适配你的项目**：以上版本更新和产物重建步骤是通用的；请根据你的项目版本方案进行定制
+8. **里程碑联动**：发布时自动创建下一轮里程碑；如果里程碑体系未初始化，建议先运行 `init-milestones`
 
 ## 错误处理
 
 - 版本格式无效：提示正确格式并退出
 - 工作区不干净：提示提交或暂存
+- 验证失败：显示失败的检查并停止发布流程
+- 产物重建失败：显示构建错误并停止发布流程
 - Git 操作失败：显示错误并提供回滚说明

package/templates/.agents/skills/review-task/SKILL.md

@@ -18,7 +18,7 @@ description: >
 ### 1. Verify Prerequisites
 
 Check required files:
-- `.agent-workspace/active/{task-id}/task.md` - Task file
+- `.agents/workspace/active/{task-id}/task.md` - Task file
 - At least one implementation report: `implementation.md` or `implementation-r{N}.md`
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, for example `TASK-20260306-143022`
@@ -27,7 +27,7 @@ If either file is missing, prompt the user to complete the prerequisite step fir
 
 ### 2. Determine Review Round
 
-Scan review artifacts in `.agent-workspace/active/{task-id}/`:
+Scan review artifacts in `.agents/workspace/active/{task-id}/`:
 - If neither `review.md` nor `review-r*.md` exists -> this is Round 1 and must create `review.md`
 - If `review.md` exists and no `review-r*.md` exists -> this is Round 2 and must create `review-r2.md`
 - If `review-r{N}.md` exists -> this is Round N+1 and must create `review-r{N+1}.md`
@@ -56,7 +56,7 @@ Follow the `code-review` step in `.agents/workflows/feature-development.yaml`:
 **Required review areas**:
 - [ ] Code quality and coding standards (per project instructions)
 - [ ] Bug and risk detection
-- [ ] Test coverage and test quality
+- [ ] Test coverage and test quality (when a feature is removed, verify that test fixtures and assertions for that feature are also removed — not mechanically flipped; assertions that only confirm data passes through unchanged are not valid tests)
 - [ ] Error handling and edge cases
 - [ ] Performance and security concerns
 - [ ] Code comments and documentation
@@ -72,7 +72,7 @@ Also review `git diff` to inspect the full context of all changes.
 
 ### 5. Output Review Report
 
-Create `.agent-workspace/active/{task-id}/{review-artifact}`.
+Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 
 ### 6. Update Task Status
 
@@ -82,7 +82,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: code-review
 - `assigned_to`: {reviewer}
 - `updated_at`: {current time}
@@ -123,7 +123,7 @@ Next step - commit changes:
 ```
 Code review complete for task {task-id}. Verdict: Approved.
 - Blockers: 0 | Major issues: {n} | Minor issues: {n}
-- Review report: .agent-workspace/active/{task-id}/{review-artifact}
+- Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - fix issues before commit (recommended):
   - Claude Code / OpenCode: /refine-task {task-id}
@@ -140,7 +140,7 @@ Or commit directly (skip fixes):
 ```
 Code review complete for task {task-id}. Verdict: Changes Requested.
 - Blockers: {n} | Major issues: {n} | Minor issues: {n}
-- Review report: .agent-workspace/active/{task-id}/{review-artifact}
+- Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - refine the issues:
   - Claude Code / OpenCode: /refine-task {task-id}
@@ -151,7 +151,7 @@ Next step - refine the issues:
 **📋 Output Branch D - Rejected** (Condition: major rework, redesign, or re-implementation is required):
 ```
 Code review complete for task {task-id}. Verdict: Rejected, major rework required.
-- Review report: .agent-workspace/active/{task-id}/{review-artifact}
+- Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - re-implement:
   - Claude Code / OpenCode: /implement-task {task-id}
@@ -264,7 +264,7 @@ Next step - re-implement:
 ## Completion Checklist
 
 - [ ] Completed code review for all modified files
-- [ ] Created review report `.agent-workspace/active/{task-id}/{review-artifact}`
+- [ ] Created review report `.agents/workspace/active/{task-id}/{review-artifact}`
 - [ ] Updated `current_step` to code-review in task.md
 - [ ] Updated `updated_at` to the current time in task.md
 - [ ] Updated `assigned_to` to the reviewer name in task.md

package/templates/.agents/skills/review-task/SKILL.zh-CN.md

@@ -17,7 +17,7 @@ description: >
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+- `.agents/workspace/active/{task-id}/task.md` - 任务文件
 - 至少一个实现报告：`implementation.md` 或 `implementation-r{N}.md`
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
@@ -26,7 +26,7 @@ description: >
 
 ### 2. 确定审查轮次
 
-扫描 `.agent-workspace/active/{task-id}/` 目录中的审查产物文件：
+扫描 `.agents/workspace/active/{task-id}/` 目录中的审查产物文件：
 - 如果不存在 `review.md` 且不存在 `review-r*.md` → 本轮为第 1 轮，产出 `review.md`
 - 如果存在 `review.md` 且不存在 `review-r*.md` → 本轮为第 2 轮，产出 `review-r2.md`
 - 如果存在 `review-r{N}.md` → 本轮为第 N+1 轮，产出 `review-r{N+1}.md`
@@ -55,7 +55,7 @@ description: >
 **必要审查领域**：
 - [ ] 代码质量和编码规范（按项目指南）
 - [ ] Bug 和潜在问题检测
-- [ ] 测试覆盖率和测试质量
+- [ ] 测试覆盖率和测试质量（删除功能时，确认为该功能而存在的测试 fixture 和断言已一并删除，而非机械翻转断言方向；仅确认数据原样通过的断言不构成有效测试）
 - [ ] 错误处理和边界情况
 - [ ] 性能和安全问题
 - [ ] 代码注释和文档
@@ -71,7 +71,7 @@ description: >
 
 ### 5. 输出审查报告
 
-创建 `.agent-workspace/active/{task-id}/{review-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{review-artifact}`。
 
 ### 6. 更新任务状态
 
@@ -81,7 +81,7 @@ description: >
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：code-review
 - `assigned_to`：{审查者}
 - `updated_at`：{当前时间}
@@ -122,7 +122,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ```
 任务 {task-id} 代码审查完成。结论：通过。
 - 阻塞项：0 | 主要问题：{n} | 次要问题：{n}
-- 审查报告：.agent-workspace/active/{task-id}/{review-artifact}
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修复问题后提交（推荐）：
   - Claude Code / OpenCode：/refine-task {task-id}
@@ -139,7 +139,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ```
 任务 {task-id} 代码审查完成。结论：需要修改。
 - 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}
-- 审查报告：.agent-workspace/active/{task-id}/{review-artifact}
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修复问题：
   - Claude Code / OpenCode：/refine-task {task-id}
@@ -150,7 +150,7 @@ date "+%Y-%m-%d %H:%M:%S"
 **📋 输出分支 D — 拒绝**（条件：需要重大返工、重新设计或重新实现）：
 ```
 任务 {task-id} 代码审查完成。结论：拒绝，需要重大返工。
-- 审查报告：.agent-workspace/active/{task-id}/{review-artifact}
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 重新实现：
   - Claude Code / OpenCode：/implement-task {task-id}
@@ -263,7 +263,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ## 完成检查清单
 
 - [ ] 完成了所有修改文件的代码审查
-- [ ] 创建了审查报告 `.agent-workspace/active/{task-id}/{review-artifact}`
+- [ ] 创建了审查报告 `.agents/workspace/active/{task-id}/{review-artifact}`
 - [ ] 更新了 task.md 中的 `current_step` 为 code-review
 - [ ] 更新了 task.md 中的 `updated_at` 为当前时间
 - [ ] 更新了 task.md 中的 `assigned_to` 为审查者名称