@fitlab-ai/agent-infra 0.3.0

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

@@ -0,0 +1,218 @@
+---
+name: commit
+description: >
+  Commit current changes to Git, including copyright header year
+  check and task status update. Triggered when the user requests
+  a code commit or save changes.
+---
+
+# Commit Changes
+
+Commit current changes to Git.
+
+## Step 0: Check Local Modifications (CRITICAL)
+
+**Mandatory**: Before any edits, you **must** check the user's local modifications to avoid overwriting their work.
+
+```bash
+git status --short
+git diff
+```
+
+**Rules**:
+1. **Read `git diff` output carefully** - understand what the user has already changed
+2. **Make incremental edits** on top of user modifications - do not overwrite their implementation
+3. **If your planned edits conflict** with user modifications, ask the user first:
+   ```
+   This file has local modifications:
+   - Your changes: [describe user's changes]
+   - My planned changes: [describe planned changes]
+   Please confirm how to proceed.
+   ```
+4. **Do NOT** rewrite code the user has already implemented
+5. **Do NOT** add "improvements" the user didn't ask for
+
+## Step 1: Update Copyright Header Years (CRITICAL)
+
+**Mandatory**: Before committing, check and update copyright headers in all modified files.
+
+### Get Current Year
+
+```bash
+date +%Y
+```
+
+**Never hardcode the year.**
+
+### Check Modified Files
+
+```bash
+git status --short
+```
+
+### For Each Modified File
+
+Check if the file has a copyright header:
+```bash
+grep "Copyright.*[0-9]\{4\}" <modified_file>
+```
+
+If it has a copyright header and the year is not current, update the year.
+
+**Common formats**:
+- `Copyright (C) 2024-2025` -> `Copyright (C) 2024-{CURRENT_YEAR}`
+- `Copyright (C) 2024` -> `Copyright (C) 2024-{CURRENT_YEAR}`
+- `Copyright (C) 2025` -> `Copyright (C) {CURRENT_YEAR}` (if already current)
+
+### Copyright Checklist
+
+Before executing `git commit`:
+- [ ] Used `date +%Y` to dynamically get the current year
+- [ ] Checked all files about to be committed
+- [ ] Updated copyright year in all files that have copyright headers
+- [ ] **Never** hardcoded the year
+- [ ] **Only** updated modified files, not the entire project
+
+## Step 2: Analyze Changes and Generate Commit Message
+
+```bash
+git status
+git diff
+git log --oneline -5
+```
+
+Generate commit message in Conventional Commits format:
+- `<type>(<scope>): <subject>` (English imperative mood, max 50 chars)
+- Body: 2-4 bullet points explaining what and why
+- Signature block:
+  - `Co-Authored-By: {Your Model Name} <noreply@provider.com>`
+  - If task-related, append extra `Co-Authored-By` lines for other contributing agents
+
+### Multi-Agent Co-Authorship (If Task-Related)
+
+If the commit belongs to an active task and `.agent-workspace/active/{task-id}/task.md` exists:
+
+1. Read the `## Activity Log` section from `task.md`.
+2. Extract all unique agent names from entries matching `by {agent}`. A loose pattern such as `by (\S+)` is acceptable.
+3. Exclude `human` because the Git author is already the human user.
+4. Map each agent to a `Co-Authored-By` line:
+
+| Agent | Signature |
+|-------|-----------|
+| `claude` | `Co-Authored-By: Claude <noreply@anthropic.com>` |
+| `codex` | `Co-Authored-By: Codex <noreply@openai.com>` |
+| `gemini` | `Co-Authored-By: Gemini <noreply@google.com>` |
+| `opencode` | `Co-Authored-By: OpenCode <noreply@opencode.ai>` |
+
+5. Build the signature block with these rules:
+   - Keep the current executing agent's signature in its original position.
+   - Append other unique participating agents as additional `Co-Authored-By` lines.
+   - Do not duplicate the current agent if it already appears in `Activity Log`.
+   - For unknown agent names, use `Co-Authored-By: {Agent} <noreply@unknown>`.
+
+If the commit is not task-related, keep the existing single-signature behavior.
+
+## Step 3: Create Commit
+
+```bash
+git add <specific-files>
+git commit -m "$(cat <<'EOF'
+<type>(<scope>): <subject>
+
+- <bullet point 1>
+- <bullet point 2>
+
+Co-Authored-By: {Your Model Name} <noreply@provider.com>
+<additional Co-Authored-By lines for other task participants, if any>
+EOF
+)"
+```
+
+**Important**:
+- Add specific files by name - do NOT use `git add -A` or `git add .`
+- Do NOT commit files that may contain secrets (.env, credentials, keys)
+- For task-related commits, keep the current agent first and append the extra lines generated above
+
+## Step 4: Update Task Status (If Task-Related)
+
+Get the current time:
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+After committing, update task status based on the situation:
+
+For all cases below, **append** to `## Activity Log` in task.md (do NOT overwrite previous entries):
+```
+- {yyyy-MM-dd HH:mm:ss} — **Commit** by {agent} — {commit hash short} {commit subject}
+```
+
+### Case 1: Final Commit (Task Complete)
+
+If this is the last commit and all work is done:
+
+Prerequisites:
+- [ ] All code committed
+- [ ] All tests pass
+- [ ] Code review passed
+- [ ] All workflow steps complete
+
+Suggest next step:
+
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
+```
+Next step - complete and archive the task:
+  - Claude Code / OpenCode: /complete-task {task-id}
+  - Gemini CLI: /{{project}}:complete-task {task-id}
+  - Codex CLI: $complete-task {task-id}
+```
+
+### Case 2: More Work Needed
+
+If there's follow-up work (awaiting review, more fixes needed):
+- Update `task.md`: set `updated_at` to current time
+- Record this commit's content and next steps in task.md
+
+### Case 3: Ready for Review
+
+If the commit is ready for code review:
+- Update `task.md`: set `current_step` to `code-review`
+- Update `task.md`: set `updated_at` to current time
+- Mark implementation step as complete in workflow progress
+
+Suggest next step:
+
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
+```
+Next step - code review:
+  - Claude Code / OpenCode: /review-task {task-id}
+  - Gemini CLI: /{{project}}:review-task {task-id}
+  - Codex CLI: $review-task {task-id}
+```
+
+### Case 4: Ready for PR
+
+If the commit should become a Pull Request:
+- Update `task.md`: set `updated_at` to current time
+- Record PR plan in task.md
+
+Suggest next step:
+
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
+```
+Next step - create a Pull Request:
+  - Claude Code / OpenCode: /create-pr
+  - Gemini CLI: /{{project}}:create-pr
+  - Codex CLI: $create-pr
+```
+
+## Notes
+
+- Do NOT commit files containing sensitive information (.env, credentials, etc.)
+- Ensure commit messages clearly describe the changes
+- Follow the project's Conventional Commits conventions
+- If task status update fails, warn the user but do not block the commit

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

@@ -0,0 +1,217 @@
+---
+name: commit
+description: >
+  提交当前变更到 Git，包含版权头年份检查和任务状态更新。
+  当用户要求提交代码或保存变更时触发。
+---
+
+# 提交代码
+
+提交当前变更到 Git。
+
+## 步骤 0：检查本地修改（关键）
+
+**强制步骤**：在任何编辑之前，你**必须**检查用户的本地修改以避免覆盖其工作。
+
+```bash
+git status --short
+git diff
+```
+
+**规则**：
+1. **仔细阅读 `git diff` 输出** —— 理解用户已经做了哪些修改
+2. **在用户修改基础上进行增量编辑** —— 不要覆盖其实现
+3. **如果你计划的编辑与用户修改冲突**，先询问用户：
+   ```
+   This file has local modifications:
+   - Your changes: [描述用户的修改]
+   - My planned changes: [描述计划的修改]
+   Please confirm how to proceed.
+   ```
+4. **不要**重写用户已实现的代码
+5. **不要**添加用户没有要求的"改进"
+
+## 步骤 1：更新版权头年份（关键）
+
+**强制步骤**：提交之前，检查并更新所有修改文件的版权头。
+
+### 获取当前年份
+
+```bash
+date +%Y
+```
+
+**绝不硬编码年份。**
+
+### 检查修改的文件
+
+```bash
+git status --short
+```
+
+### 对每个修改的文件
+
+检查文件是否有版权头：
+```bash
+grep "Copyright.*[0-9]\{4\}" <modified_file>
+```
+
+如果有版权头且年份不是当前年份，更新年份。
+
+**常见格式**：
+- `Copyright (C) 2024-2025` -> `Copyright (C) 2024-{CURRENT_YEAR}`
+- `Copyright (C) 2024` -> `Copyright (C) 2024-{CURRENT_YEAR}`
+- `Copyright (C) 2025` -> `Copyright (C) {CURRENT_YEAR}`（如果已是当前年份）
+
+### 版权检查清单
+
+执行 `git commit` 之前：
+- [ ] 使用 `date +%Y` 动态获取当前年份
+- [ ] 检查了所有即将提交的文件
+- [ ] 更新了所有有版权头的文件的版权年份
+- [ ] **绝不**硬编码年份
+- [ ] **仅**更新修改的文件，而非整个项目
+
+## 步骤 2：分析变更并生成提交信息
+
+```bash
+git status
+git diff
+git log --oneline -5
+```
+
+生成 Conventional Commits 格式的提交信息：
+- `<type>(<scope>): <subject>`（英文祈使语气，不超过 50 字符）
+- Body：2-4 个要点说明修改了什么以及为什么
+- 署名块：
+  - `Co-Authored-By: {你的模型名称} <noreply@provider.com>`
+  - 如果与任务相关，追加其他贡献 Agent 的 `Co-Authored-By` 行
+
+### 多 Agent 协作署名（仅任务相关提交）
+
+如果本次提交属于某个活动任务，且存在 `.agent-workspace/active/{task-id}/task.md`：
+
+1. 读取 `task.md` 中的 `## Activity Log` 部分。
+2. 从符合 `by {agent}` 的条目中提取所有唯一 Agent 名称；可使用较宽松的匹配模式，例如 `by (\S+)`。
+3. 排除 `human`，因为 Git author 已经是人类用户。
+4. 将 Agent 名称映射为 `Co-Authored-By` 行：
+
+| Agent | 署名 |
+|-------|------|
+| `claude` | `Co-Authored-By: Claude <noreply@anthropic.com>` |
+| `codex` | `Co-Authored-By: Codex <noreply@openai.com>` |
+| `gemini` | `Co-Authored-By: Gemini <noreply@google.com>` |
+| `opencode` | `Co-Authored-By: OpenCode <noreply@opencode.ai>` |
+
+5. 构建署名块时遵循以下规则：
+   - 保持当前执行提交的 Agent 署名在原有位置。
+   - 将其他唯一参与 Agent 作为额外的 `Co-Authored-By` 行追加。
+   - 如果当前 Agent 已在 `Activity Log` 中出现，不要重复追加。
+   - 未知 Agent 名称使用兜底格式 `Co-Authored-By: {Agent} <noreply@unknown>`。
+
+如果本次提交与任务无关，保持原有单行署名行为不变。
+
+## 步骤 3：创建提交
+
+```bash
+git add <specific-files>
+git commit -m "$(cat <<'EOF'
+<type>(<scope>): <subject>
+
+- <要点 1>
+- <要点 2>
+
+Co-Authored-By: {你的模型名称} <noreply@provider.com>
+<其他任务参与者的额外 Co-Authored-By 行（如有）>
+EOF
+)"
+```
+
+**重要**：
+- 按名称添加特定文件 —— 不要使用 `git add -A` 或 `git add .`
+- 不要提交可能包含密钥的文件（.env、凭据、密钥）
+- 对于任务相关提交，保持当前 Agent 署名在前，并在其后追加上面生成的额外署名行
+
+## 步骤 4：更新任务状态（如果与任务相关）
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+提交后，根据情况更新任务状态：
+
+对于以下所有情况，**追加**到 task.md 的 `## Activity Log`（不要覆盖之前的记录）：
+```
+- {yyyy-MM-dd HH:mm:ss} — **Commit** by {agent} — {commit hash short} {commit subject}
+```
+
+### 情况 1：最终提交（任务完成）
+
+如果这是最后一次提交且所有工作已完成：
+
+前置条件：
+- [ ] 所有代码已提交
+- [ ] 所有测试通过
+- [ ] 代码审查通过
+- [ ] 所有工作流步骤完成
+
+建议下一步：
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+下一步 - 完成并归档任务：
+  - Claude Code / OpenCode：/complete-task {task-id}
+  - Gemini CLI：/{{project}}:complete-task {task-id}
+  - Codex CLI：$complete-task {task-id}
+```
+
+### 情况 2：还有后续工作
+
+如果有后续工作（等待审查、需要更多修复）：
+- 更新 `task.md`：设置 `updated_at` 为当前时间
+- 在 task.md 中记录此次提交的内容和下一步
+
+### 情况 3：准备审查
+
+如果提交已准备好进行代码审查：
+- 更新 `task.md`：设置 `current_step` 为 `code-review`
+- 更新 `task.md`：设置 `updated_at` 为当前时间
+- 在工作流进度中标记 implementation 步骤为已完成
+
+建议下一步：
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+下一步 - 代码审查：
+  - Claude Code / OpenCode：/review-task {task-id}
+  - Gemini CLI：/{{project}}:review-task {task-id}
+  - Codex CLI：$review-task {task-id}
+```
+
+### 情况 4：准备创建 PR
+
+如果提交应该创建 Pull Request：
+- 更新 `task.md`：设置 `updated_at` 为当前时间
+- 在 task.md 中记录 PR 计划
+
+建议下一步：
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+下一步 - 创建 Pull Request：
+  - Claude Code / OpenCode：/create-pr
+  - Gemini CLI：/{{project}}:create-pr
+  - Codex CLI：$create-pr
+```
+
+## 注意事项
+
+- 不要提交包含敏感信息的文件（.env、凭据等）
+- 确保提交信息清晰描述变更内容
+- 遵循项目的 Conventional Commits 规范
+- 如果任务状态更新失败，警告用户但不要阻止提交

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

@@ -0,0 +1,139 @@
+---
+name: complete-task
+description: >
+  Mark a task as completed and archive it by moving the task directory from
+  active/ to completed/. Verifies that all workflow steps are done, code is
+  reviewed and committed, and tests pass before allowing completion.
+  Triggered when the user requests task completion or archiving.
+  Argument: task-id.
+---
+
+# Complete Task
+
+## Boundary / Critical Rules
+
+- This command updates task metadata AND physically moves the task directory
+- Do not archive a task that has incomplete workflow steps unless forced
+
+## Steps
+
+### 1. Verify Task Exists
+
+Check that the task exists in `.agent-workspace/active/{task-id}/`.
+
+Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, e.g. `TASK-20260306-143022`
+
+If not found in `active/`, check `blocked/` and `completed/`:
+- If in `completed/`: Inform user the task is already completed
+- If in `blocked/`: Inform user the task is blocked; suggest unblocking first
+
+### 2. Verify Completion Prerequisites
+
+Before marking complete, verify ALL of these:
+- [ ] All workflow steps are complete (check workflow progress in task.md)
+- [ ] Code has been reviewed (`review.md` or `review-r{N}.md` exists, and the latest review verdict is Approved; or review was done externally)
+- [ ] Code has been committed (no uncommitted changes related to this task)
+- [ ] Tests are passing
+
+If any prerequisite is not met, warn the user:
+```
+Cannot complete task {task-id} - prerequisites not met:
+- [ ] {Missing prerequisite}
+
+Please complete the missing steps first, or use --force to override.
+```
+
+### 3. Update Task Metadata
+
+Get the current time:
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+Update `.agent-workspace/active/{task-id}/task.md`:
+- `status`: completed
+- `completed_at`: {current timestamp}
+- `updated_at`: {current timestamp}
+- Mark all workflow steps as complete
+- **Append** to `## Activity Log` (do NOT overwrite previous entries):
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/
+  ```
+
+### 4. Archive Task
+
+Move the task directory from active to completed:
+
+```bash
+mv .agent-workspace/active/{task-id} .agent-workspace/completed/{task-id}
+```
+
+### 5. Verify Archive
+
+```bash
+ls .agent-workspace/completed/{task-id}/task.md
+```
+
+Confirm the task directory was successfully moved.
+
+### 6. Sync to Issue (Optional)
+
+Check whether `task.md` includes an `issue_number` field whose value is neither empty nor `N/A`. If not, **skip this step and output nothing**.
+
+If a valid `issue_number` exists, optionally sync the completion status:
+
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
+```
+(Optional) Sync completion status to the GitHub Issue:
+  - Claude Code / OpenCode: /sync-issue {issue_number}
+  - Gemini CLI: /{{project}}:sync-issue {issue_number}
+  - Codex CLI: $sync-issue {issue_number}
+```
+
+### 7. Inform User
+
+Output format:
+```
+Task {task-id} completed and archived.
+
+Task info:
+- Title: {title}
+- Completed at: {timestamp}
+- Archived to: .agent-workspace/completed/{task-id}/
+
+Deliverables:
+- {List of key outputs: files modified, tests added, etc.}
+```
+
+## Completion Checklist
+
+- [ ] Verified all workflow steps are complete
+- [ ] Updated task.md with completed status and timestamp
+- [ ] Moved task directory to `.agent-workspace/completed/`
+- [ ] Verified archive succeeded
+- [ ] Informed user of completion
+
+## Notes
+
+1. **Premature completion**: Do not archive a task that has incomplete steps. Examples of incomplete situations:
+   - Code is written but not committed
+   - Code is committed but not reviewed
+   - Review found blockers that haven't been fixed
+   - PR is created but not merged
+
+2. **Rollback**: If a task was archived incorrectly:
+   ```bash
+   mv .agent-workspace/completed/{task-id} .agent-workspace/active/{task-id}
+   ```
+   Then update task.md status back to `active`.
+
+3. **Multiple contributors**: If multiple AI agents worked on the task, ensure all contributions are committed before completing.
+
+## Error Handling
+
+- Task not found: Prompt "Task {task-id} not found in active directory"
+- Already completed: Prompt "Task {task-id} is already in completed directory"
+- Task is blocked: Prompt "Task {task-id} is blocked. Unblock it first by moving to active/"
+- Move failed: Prompt error and suggest manual move

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

@@ -0,0 +1,137 @@
+---
+name: complete-task
+description: >
+  标记任务完成并归档，将任务目录从 active/ 移动到 completed/。在允许完成之前，
+  验证所有工作流步骤已完成、代码已审查并提交、测试已通过。
+  当用户要求完成或归档任务时触发。参数：task-id。
+---
+
+# 完成任务
+
+## 行为边界 / 关键规则
+
+- 本命令更新任务元数据并物理移动任务目录
+- 除非强制执行，不要归档有未完成工作流步骤的任务
+
+## 执行步骤
+
+### 1. 验证任务存在
+
+检查任务是否存在于 `.agent-workspace/active/{task-id}/`。
+
+注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
+
+如果在 `active/` 中未找到，检查 `blocked/` 和 `completed/`：
+- 如果在 `completed/`：告知用户任务已完成
+- 如果在 `blocked/`：告知用户任务被阻塞；建议先解除阻塞
+
+### 2. 验证完成前置条件
+
+标记完成之前，验证以下所有条件：
+- [ ] 所有工作流步骤已完成（检查 task.md 中的工作流进度）
+- [ ] 代码已审查（`review.md` 或 `review-r{N}.md` 存在，且最新审查结论为 Approved；或已在外部完成审查）
+- [ ] 代码已提交（没有与此任务相关的未提交变更）
+- [ ] 测试通过
+
+如果任何前置条件未满足，警告用户：
+```
+Cannot complete task {task-id} - prerequisites not met:
+- [ ] {缺失的前置条件}
+
+Please complete the missing steps first, or use --force to override.
+```
+
+### 3. 更新任务元数据
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+更新 `.agent-workspace/active/{task-id}/task.md`：
+- `status`：completed
+- `completed_at`：{当前时间戳}
+- `updated_at`：{当前时间戳}
+- 标记所有工作流步骤为已完成
+- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/
+  ```
+
+### 4. 归档任务
+
+将任务目录从 active 移动到 completed：
+
+```bash
+mv .agent-workspace/active/{task-id} .agent-workspace/completed/{task-id}
+```
+
+### 5. 验证归档
+
+```bash
+ls .agent-workspace/completed/{task-id}/task.md
+```
+
+确认任务目录已成功移动。
+
+### 6. 同步到 Issue（可选）
+
+检查 `task.md` 中是否存在 `issue_number` 字段，且其值不为空也不为 `N/A`。如果没有，**跳过此步骤，不输出任何内容**。
+
+如果存在有效的 `issue_number`，可选择同步完成状态：
+
+> **重要**：以下列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+```
+（可选）同步完成状态到 GitHub Issue：
+  - Claude Code / OpenCode：/sync-issue {issue_number}
+  - Gemini CLI：/{{project}}:sync-issue {issue_number}
+  - Codex CLI：$sync-issue {issue_number}
+```
+
+### 7. 告知用户
+
+输出格式：
+```
+任务 {task-id} 已完成并归档。
+
+任务信息：
+- 标题：{title}
+- 完成时间：{timestamp}
+- 归档路径：.agent-workspace/completed/{task-id}/
+
+交付物：
+- {关键产出列表：修改的文件、添加的测试等}
+```
+
+## 完成检查清单
+
+- [ ] 验证了所有工作流步骤已完成
+- [ ] 更新了 task.md 的完成状态和时间戳
+- [ ] 将任务目录移动到 `.agent-workspace/completed/`
+- [ ] 验证了归档成功
+- [ ] 告知了用户完成情况
+
+## 注意事项
+
+1. **过早完成**：不要归档有未完成步骤的任务。未完成的情况示例：
+   - 代码已编写但未提交
+   - 代码已提交但未审查
+   - 审查发现阻塞项但未修复
+   - PR 已创建但未合并
+
+2. **回滚**：如果任务被错误归档：
+   ```bash
+   mv .agent-workspace/completed/{task-id} .agent-workspace/active/{task-id}
+   ```
+   然后将 task.md 中的状态改回 `active`。
+
+3. **多贡献者**：如果多个 AI 代理参与了任务，确保所有贡献都已提交后再完成。
+
+## 错误处理
+
+- 任务未找到：提示 "Task {task-id} not found in active directory"
+- 已完成：提示 "Task {task-id} is already in completed directory"
+- 任务被阻塞：提示 "Task {task-id} is blocked. Unblock it first by moving to active/"
+- 移动失败：提示错误并建议手动移动