@fitlab-ai/agent-infra 0.4.0 → 0.4.2

package/templates/.agents/skills/refine-task/reference/report-template.md

@@ -0,0 +1,38 @@
+# Refinement Report Template
+
+Use this structure when writing `refinement.md` or `refinement-r{N}.md`.
+
+## Output Template
+
+```markdown
+# Refinement Report
+
+- **Refinement Round**: Round {refinement-round}
+- **Artifact File**: `{refinement-artifact}`
+- **Review Input**: `{review-artifact}`
+- **Implementation Context**: `{implementation-artifact}`
+
+### Review Feedback Handling
+
+#### Blocker Fixes
+1. **{issue-title}**
+   - **Fix**: {what changed}
+   - **File**: `{file-path}:{line-number}`
+   - **Validation**: {validation}
+
+#### Major Issue Fixes
+1. **{issue-title}**
+   - **Fix**: {what changed}
+   - **File**: `{file-path}:{line-number}`
+
+#### Minor Issue Handling
+1. **{issue-title}**
+   - **Fix**: {what changed}
+
+#### Unresolved Issues
+- {issue}: {reason}
+
+### Test Results After Refinement
+- All tests passing: {yes/no}
+- Test output: {summary}
+```

package/templates/.agents/skills/refine-task/reference/report-template.zh-CN.md

@@ -0,0 +1,38 @@
+# 修复报告模板
+
+编写 `refinement.md` 或 `refinement-r{N}.md` 时，使用以下结构。
+
+## 输出模板
+
+```markdown
+# 修复报告
+
+- **修复轮次**: Round {refinement-round}
+- **产物文件**: `{refinement-artifact}`
+- **审查输入**: `{review-artifact}`
+- **实现上下文**: `{implementation-artifact}`
+
+### 审查反馈处理
+
+#### 阻塞项修复
+1. **{issue-title}**
+   - **修复**: {what changed}
+   - **文件**: `{file-path}:{line-number}`
+   - **验证**: {validation}
+
+#### 主要问题修复
+1. **{issue-title}**
+   - **修复**: {what changed}
+   - **文件**: `{file-path}:{line-number}`
+
+#### 次要问题处理
+1. **{issue-title}**
+   - **修复**: {what changed}
+
+#### 未解决问题
+- {issue}: {reason}
+
+### 修复后的测试结果
+- 所有测试通过: {yes/no}
+- 测试输出: {summary}
+```

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

@@ -1,9 +1,6 @@
 ---
 name: refine-title
-description: >
-  Deeply analyze Issue or PR content and reformat the title to
-  Conventional Commits format. Triggered when the user requests
-  title optimization. Argument: issue or PR number.
+description: "Rewrite an Issue or PR title in Conventional Commits format"
 ---
 
 # Refine Title

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

@@ -1,8 +1,6 @@
 ---
 name: refine-title
-description: >
-  深度分析 Issue 或 PR 内容，并将其标题重构为 Conventional Commits 格式。
-  当用户要求优化标题时触发。参数：issue 或 PR 编号。
+description: "重构 Issue/PR 标题为 Conventional Commits 格式"
 ---
 
 # 重构标题

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

@@ -1,8 +1,6 @@
 ---
 name: release
-description: >
-  Execute the version release workflow. Triggered when the user
-  requests a version release. Argument: version number (X.Y.Z).
+description: "Run the version release workflow"
 ---
 
 # Version Release
@@ -13,7 +11,7 @@ Execute the version release workflow for the specified version.
 
 ## Execution Flow
 
-### Step 1: Parse and Validate Version
+### 1. Parse and Validate Version
 
 Extract version from arguments. Must match `X.Y.Z` format.
 
@@ -23,7 +21,7 @@ Parse components:
 
 If format is invalid, error: "Version format incorrect, expected X.Y.Z (e.g. 1.2.3)"
 
-### Step 2: Verify Clean Workspace
+### 2. Verify Clean Workspace
 
 ```bash
 git status --short
@@ -31,7 +29,7 @@ git status --short
 
 If there are uncommitted changes, error: "Workspace has uncommitted changes. Please commit or stash first."
 
-### Step 3: Pre-release Verification
+### 3. Pre-release Verification
 
 <!-- TODO: Replace with your project's pre-release verification steps -->
 
@@ -50,7 +48,7 @@ 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
+### 4. Update Version References
 
 <!-- TODO: Replace with your project's version update steps -->
 
@@ -76,7 +74,7 @@ Search for version references in project files and update them:
 
 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
+### 5. Rebuild Artifacts
 
 <!-- TODO: Replace with your project's artifact rebuild steps -->
 
@@ -91,20 +89,20 @@ Execution guidance:
 - 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
+### 6. Create Release Commit
 
 ```bash
 git add -A
 git commit -m "chore: release v{version}"
 ```
 
-### Step 7: Create Git Tag
+### 7. Create Git Tag
 
 ```bash
 git tag v{version}
 ```
 
-### Step 8: Manage Milestones
+### 8. Manage Milestones
 
 Close the milestone for the released version when it exists, and create the missing planning milestones for the next cycle.
 
@@ -121,7 +119,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 9: Output Summary
+### 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.
 

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

@@ -1,7 +1,6 @@
 ---
 name: release
-description: >
-  执行版本发布流程。当用户要求发布版本时触发。参数：版本号（X.Y.Z）。
+description: "执行版本发布流程"
 ---
 
 # 版本发布
@@ -12,7 +11,7 @@ description: >
 
 ## 执行流程
 
-### 步骤 1：解析并验证版本号
+### 1. 解析并验证版本号
 
 从参数中提取版本。必须匹配 `X.Y.Z` 格式。
 
@@ -22,7 +21,7 @@ description: >
 
 如果格式无效，报错："Version format incorrect, expected X.Y.Z (e.g. 1.2.3)"
 
-### 步骤 2：验证工作区干净
+### 2. 验证工作区干净
 
 ```bash
 git status --short
@@ -30,7 +29,7 @@ git status --short
 
 如果有未提交的变更，报错："Workspace has uncommitted changes. Please commit or stash first."
 
-### 步骤 3：发布前验证
+### 3. 发布前验证
 
 <!-- TODO: 替换为你的项目发布前验证步骤 -->
 
@@ -49,7 +48,7 @@ git branch --show-current
 - 如果当前分支不符合预期，按项目策略输出警告或直接退出
 - 如果任何验证命令失败，停止发布流程并先修复问题
 
-### 步骤 4：更新版本引用
+### 4. 更新版本引用
 
 <!-- TODO: 替换为你的项目版本更新步骤 -->
 
@@ -75,7 +74,7 @@ git branch --show-current
 
 如果项目使用 `package-lock.json`，在更新 `package.json` 后运行 `npm install --package-lock-only`，确保锁文件中的版本号保持同步。
 
-### 步骤 5：重新生成构建产物
+### 5. 重新生成构建产物
 
 <!-- TODO: 替换为你的项目产物重建步骤 -->
 
@@ -90,20 +89,20 @@ git branch --show-current
 - 如果项目没有生成产物，请在项目特化版本中明确说明
 - 如果重建失败，停止发布流程并先修复构建问题
 
-### 步骤 6：创建发布提交
+### 6. 创建发布提交
 
 ```bash
 git add -A
 git commit -m "chore: release v{version}"
 ```
 
-### 步骤 7：创建 Git 标签
+### 7. 创建 Git 标签
 
 ```bash
 git tag v{version}
 ```
 
-### 步骤 8：管理里程碑
+### 8. 管理里程碑
 
 为已发布版本关闭对应版本里程碑，并为下一轮创建缺失的规划里程碑。
 
@@ -120,7 +119,7 @@ bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PAT
 - 当 `PATCH=0` 时，同时确保 `{MAJOR}.{MINOR+1}.0` 与 `{MAJOR}.{MINOR+1}.x`
 - 输出包含已发布里程碑动作和新建数量的汇总
 
-### 步骤 9：输出摘要
+### 9. 输出摘要
 
 > **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
 

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

@@ -1,79 +1,47 @@
 ---
 name: review-task
-description: >
-  Review implemented task changes and output a code review report, categorized by
-  severity (Blocker / Major / Minor). Triggered when the user requests code
-  review after implementation is complete. Argument: task-id.
+description: "Review a task implementation and output a code review report"
 ---
 
 # Code Review
 
+Review the latest implementation round and produce `review.md` or `review-r{N}.md`.
+
 ## Boundary / Critical Rules
 
-- This skill only reads code and produces a review report (`review.md` or `review-r{N}.md`) -- it does not modify business code
-- After executing this skill, you **must** immediately update task status in task.md
+- This skill reviews code and writes a report; it does not modify product code
+- After executing this skill, you **must** immediately update task.md
 
 ## Steps
 
 ### 1. Verify Prerequisites
 
-Check required files:
-- `.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`
-
-If either file is missing, prompt the user to complete the prerequisite step first.
+Require:
+- `.agents/workspace/active/{task-id}/task.md`
+- at least one implementation artifact: `implementation.md` or `implementation-r{N}.md`
 
 ### 2. Determine Review Round
 
-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`
-
-Record:
-- `{review-round}`: the current review round
-- `{review-artifact}`: the review report filename for this round
-
-### 3. Read Implementation and Refinement Reports
-
-Scan implementation reports in the task directory (`implementation.md`, `implementation-r{N}.md`) and read the highest-round file to understand:
-- The list of modified files
-- The key functionality that was implemented
-- Test results
-- Any items the implementer marked for reviewer attention
-
-If refinement artifacts exist (`refinement.md`, `refinement-r{N}.md`), read the highest-round file to understand:
-- Which review findings were already fixed
-- The effect of those fixes on code and tests
-- How the current code state changed relative to the previous review
+Scan the task directory and record:
+- `{review-round}`
+- `{review-artifact}` as `review.md` or `review-r{N}.md`
 
-### 4. Perform Code Review
+### 3. Read Implementation and Refinement Context
 
-Follow the `code-review` step in `.agents/workflows/feature-development.yaml`:
+Read the highest-round implementation artifact and, if present, the highest-round refinement artifact.
 
-**Required review areas**:
-- [ ] Code quality and coding standards (per project instructions)
-- [ ] Bug and risk detection
-- [ ] 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
-- [ ] Alignment with the technical plan
+### 4. Perform the Review
 
-**Review principles**:
-1. **Strict but fair**: Point out issues while also calling out what was done well
-2. **Specific**: Provide exact file paths and line numbers
-3. **Actionable**: Do not only point out problems; give fix suggestions
-4. **Severity-based**: Distinguish must-fix issues from optional improvements
+Follow `.agents/workflows/feature-development.yaml` and inspect `git diff` for the full change context.
 
-Also review `git diff` to inspect the full context of all changes.
+> Detailed review criteria, severity rules, and reviewer expectations live in `reference/review-criteria.md`. Read `reference/review-criteria.md` before reviewing.
 
-### 5. Output Review Report
+### 5. Write the Review Report
 
 Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 
+> The report format and severity layout live in `reference/report-template.md`. Read `reference/report-template.md` before writing the review.
+
 ### 6. Update Task Status
 
 Get the current time:
@@ -82,205 +50,35 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agents/workspace/active/{task-id}/task.md`:
-- `current_step`: code-review
-- `assigned_to`: {reviewer}
-- `updated_at`: {current time}
-- Record the review artifact for this round: `{review-artifact}` (Round `{review-round}`)
-- Mark code-review as complete in workflow progress and include the actual round when the task template supports it
-- **Append** to `## Activity Log` (do NOT overwrite previous entries):
-  ```
-  - {yyyy-MM-dd HH:mm:ss} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}
-  ```
+Update task.md and append:
+`- {yyyy-MM-dd HH:mm:ss} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
 
 ### 7. Inform User
 
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
-
-Output based on the review result:
-
-> **⚠️ CONDITION CHECK — you must determine the conditions below first, then choose exactly one matching output branch:**
->
-> 1. If `Blocker = 0` and `Major = 0` and `Minor = 0` -> use "Output Branch A - Passed with No Issues"
-> 2. If `Blocker = 0` and (`Major > 0` or `Minor > 0`) -> use "Output Branch B - Passed with Issues"
-> 3. If `Blocker > 0` and the issues can be resolved in a focused follow-up fix, **without requiring broad rework** -> use "Output Branch C - Changes Requested"
-> 4. If the issues require major rework, redesign, or re-implementation -> use "Output Branch D - Rejected"
->
-> **Do not skip the decision. Do not mix templates from different branches. You must output exactly one branch. As soon as `Blocker > 0`, you must not output any "Approved" template.**
-
-**📋 Output Branch A - Passed with No Issues** (Condition: Blocker = 0 and Major = 0 and Minor = 0):
-```
-Code review complete for task {task-id}. Verdict: Approved.
-- Blockers: 0 | Major issues: 0 | Minor issues: 0
-
-Next step - commit changes:
-  - Claude Code / OpenCode: /commit
-  - Gemini CLI: /{{project}}:commit
-  - Codex CLI: $commit
-```
-
-**📋 Output Branch B - Passed with Issues** (Condition: Blocker = 0 and (`Major > 0` or `Minor > 0`)):
-```
-Code review complete for task {task-id}. Verdict: Approved.
-- Blockers: 0 | Major issues: {n} | Minor issues: {n}
-- Review report: .agents/workspace/active/{task-id}/{review-artifact}
-
-Next step - fix issues before commit (recommended):
-  - Claude Code / OpenCode: /refine-task {task-id}
-  - Gemini CLI: /{{project}}:refine-task {task-id}
-  - Codex CLI: $refine-task {task-id}
-
-Or commit directly (skip fixes):
-  - Claude Code / OpenCode: /commit
-  - Gemini CLI: /{{project}}:commit
-  - Codex CLI: $commit
-```
-
-**📋 Output Branch C - Changes Requested** (Condition: Blocker > 0, and the issues are fixable without major rework):
-```
-Code review complete for task {task-id}. Verdict: Changes Requested.
-- Blockers: {n} | Major issues: {n} | Minor issues: {n}
-- Review report: .agents/workspace/active/{task-id}/{review-artifact}
-
-Next step - refine the issues:
-  - Claude Code / OpenCode: /refine-task {task-id}
-  - Gemini CLI: /{{project}}:refine-task {task-id}
-  - Codex CLI: $refine-task {task-id}
-```
-
-**📋 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: .agents/workspace/active/{task-id}/{review-artifact}
-
-Next step - re-implement:
-  - Claude Code / OpenCode: /implement-task {task-id}
-  - Gemini CLI: /{{project}}:implement-task {task-id}
-  - Codex CLI: $implement-task {task-id}
-```
-
-## Output Template
+Choose exactly one branch based on the findings:
+- no blockers, no major, no minor -> approved with no issues
+- no blockers, but major or minor findings -> approved with issues
+- blockers that can be fixed in a focused pass -> changes requested
+- major redesign or re-implementation needed -> rejected
 
-```markdown
-# Code Review Report
+> The full four-branch output templates, selection rules, and prohibition clauses live in `reference/output-templates.md`. Read `reference/output-templates.md` before reporting the review result.
 
-- **Review round**: Round {review-round}
-- **Artifact file**: `{review-artifact}`
-- **Implementation input**:
-  - `{implementation-artifact}`
-  - `{refinement-artifact}` (if present)
-
-## Review Summary
-
-- **Reviewer**: {reviewer name}
-- **Review time**: {timestamp}
-- **Review scope**: {file count and major modules}
-- **Overall verdict**: {Approved / Changes Requested / Rejected}
-
-## Findings
-
-### Blockers (must fix)
-
-#### 1. {Issue title}
-**File**: `{file-path}:{line-number}`
-**Description**: {Detailed description}
-**Suggested fix**: {Concrete suggestion}
-**Severity**: High
-
-### Major Issues (should fix)
-
-#### 1. {Issue title}
-**File**: `{file-path}:{line-number}`
-**Description**: {Detailed description}
-**Suggested fix**: {Concrete suggestion}
-**Severity**: Medium
-
-### Minor Issues (optional improvements)
-
-#### 1. {Improvement point}
-**File**: `{file-path}:{line-number}`
-**Suggestion**: {Improvement suggestion}
-
-## Highlights
-
-- {Positive aspect 1}
-- {Positive aspect 2}
-
-## Standards Compliance
-
-### Coding Standards
-- [ ] Naming conventions
-- [ ] Code style
-- [ ] Comment standards
-- [ ] Testing standards
-
-### Code Quality Metrics
-- Cyclomatic complexity: {Assessment}
-- Code duplication: {Assessment}
-- Test coverage: {Percentage or assessment}
-
-## Test Review
-
-### Test Coverage
-- Unit tests: {Assessment}
-- Edge cases: {Covered?}
-- Error scenarios: {Covered?}
-
-### Test Quality
-- Test naming: {Assessment}
-- Assertion sufficiency: {Assessment}
-- Test independence: {Assessment}
-
-## Security Review
-
-- SQL injection risk: {Check result}
-- XSS risk: {Check result}
-- Access control: {Check result}
-- Sensitive data exposure: {Check result}
-
-## Performance Review
-
-- Algorithmic complexity: {Assessment}
-- Resource management: {Check result}
-- Potential bottlenecks: {Assessment}
-
-## Alignment with Plan
-
-- [ ] Implementation matches the technical plan
-- [ ] No deviation from design intent
-- [ ] No out-of-scope functionality was added
-
-## Conclusion and Recommendation
-
-### Approval Decision
-- [ ] Approved - no blocking issues
-- [ ] Changes Requested - issues need to be resolved
-- [ ] Rejected - major rework required
-
-### Next Steps
-{Recommendation based on the review result}
-```
+Include all TUI command formats in the next-step output.
 
 ## Completion Checklist
 
-- [ ] Completed code review for all modified files
-- [ ] 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
-- [ ] Appended an Activity Log entry to task.md
-- [ ] Marked code-review as complete in workflow progress
-- [ ] Informed the user of the next step based on the review result (must include all TUI command formats without filtering)
+- [ ] Reviewed the latest implementation context
+- [ ] Created `{review-artifact}`
+- [ ] Updated task.md and appended the Activity Log entry
+- [ ] Chose exactly one verdict branch in the user output
 
 ## Notes
 
-1. **Prerequisite**: At least one implementation round must already exist (`implementation.md` or `implementation-r{N}.md`)
-2. **Objectivity**: Be strict but fair; acknowledge strong work while pointing out issues
-3. **Specificity**: Always cite exact file paths and line numbers
-4. **Severity categories**: Blockers must be fixed; major issues should be fixed; minor issues are optional
-5. **Versioning rule**: First review uses `review.md`; later rounds use `review-r{N}.md`
+- Round 1 uses `review.md`; later rounds use `review-r{N}.md`
+- Always cite concrete file paths and line numbers in findings
+- Review severity must distinguish blockers, major issues, and minor issues
 
 ## Error Handling
 
-- Task not found: Prompt "Task {task-id} not found"
-- Missing implementation report: Prompt "Implementation report not found, please run the implement-task skill first"
+- Task not found: `Task {task-id} not found`
+- Missing implementation report: `Implementation report not found, please run the implement-task skill first`