@fitlab-ai/agent-infra 0.4.4 → 0.4.5

package/README.md

@@ -380,7 +380,7 @@ The generated `.agents/.airc.json` file is the central contract between the boot
   "project": "my-project",
   "org": "my-org",
   "language": "en",
-  "templateVersion": "v0.4.4",
+  "templateVersion": "v0.4.5",
   "files": {
     "managed": [
       ".agents/workspace/README.md",

package/README.zh-CN.md

@@ -380,7 +380,7 @@ import-issue #42                    从 GitHub Issue 导入任务
   "project": "my-project",
   "org": "my-org",
   "language": "en",
-  "templateVersion": "v0.4.4",
+  "templateVersion": "v0.4.5",
   "files": {
     "managed": [
       ".agents/workspace/README.md",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fitlab-ai/agent-infra",
-  "version": "0.4.4",
+  "version": "0.4.5",
   "description": "Bootstrap tool for AI multi-tool collaboration infrastructure — works with Claude Code, Codex, Gemini CLI, and OpenCode",
   "license": "MIT",
   "type": "module",

package/templates/.agents/rules/commit-and-pr.md

@@ -0,0 +1,30 @@
+# General Rules - Commit and PR
+
+## Commit Message Format
+
+- Use Conventional Commits: `<type>(<scope>): <subject>`
+- Allowed `type` values: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`
+- `scope`: module name (optional)
+- Write the `subject` in concise imperative English
+
+## No Automatic Commits
+
+- Never run `git commit` or `git add` automatically
+- Enter the commit workflow only when the user explicitly requests a commit
+- After finishing code changes, remind the user to use the appropriate TUI commit command
+
+## PR Rules
+
+Before creating a PR, make sure:
+- all tests pass
+- code checks pass
+- the build succeeds
+- public API documentation is updated when applicable
+- copyright header years are updated when applicable
+
+## Copyright Year Updates
+
+- Run `date +%Y` first and do not hardcode the year
+- Update examples:
+  - `2024-2025` -> `2024-2026`
+  - `2024` -> `2024-2026`

package/templates/.agents/rules/commit-and-pr.zh-CN.md

@@ -0,0 +1,30 @@
+# 通用规则 - 提交与 PR
+
+## 提交信息格式
+
+- 使用 Conventional Commits：`<type>(<scope>): <subject>`
+- `type` 仅限：`feat`、`fix`、`docs`、`refactor`、`test`、`chore`
+- `scope`：模块名（可省略）
+- `subject` 使用英文祈使语气，保持简洁
+
+## 禁止自动提交
+
+- 绝对不要自动执行 `git commit` 或 `git add`
+- 仅在用户明确发起提交命令时才进入提交流程
+- 完成代码修改后，提醒用户使用对应 TUI 的提交命令
+
+## PR 提交规则
+
+创建 PR 前必须确保：
+- 所有测试通过
+- 代码检查通过
+- 构建成功
+- 公共 API 已补充文档（如适用）
+- 版权头年份已更新（如适用）
+
+## 版权年份更新
+
+- 先运行 `date +%Y` 获取当前年份，不要硬编码
+- 更新格式示例：
+  - `2024-2025` -> `2024-2026`
+  - `2024` -> `2024-2026`

package/templates/.agents/rules/issue-sync.md

@@ -88,12 +88,16 @@ Use this format:
 <!-- sync-issue:{task-id}:{file-stem} -->
 ## {artifact-title}
 
+> **{agent}** · {task-id}
+
 {artifact body}
 
 ---
-*Generated by AI · Internal tracking: {task-id}*
+*Generated by {agent} · Internal tracking: {task-id}*
 ```
 
+`{agent}` is the name of the AI agent currently executing the skill (for example `claude`, `codex`, or `gemini`).
+
 `summary` comments need extra handling:
 - find an existing `<!-- sync-issue:{task-id}:summary -->` comment ID first
 - create the comment when none exists
@@ -133,6 +137,8 @@ task.md comment format:
 <!-- sync-issue:{task-id}:task -->
 ## Task File
 
+> **{agent}** · {task-id}
+
 <details><summary>Metadata (frontmatter)</summary>
 
 ​```yaml
@@ -146,7 +152,7 @@ task.md comment format:
 {task.md body after frontmatter}
 
 ---
-*Generated by AI · Internal tracking: {task-id}*
+*Generated by {agent} · Internal tracking: {task-id}*
 ```
 
 When restoring, extract the frontmatter from the `<details>` block and reassemble with the body to recover the original `task.md`.
@@ -159,6 +165,10 @@ Title mapping:
 - Scan `task.md`, `analysis*.md`, `plan*.md`, `implementation*.md`, `review*.md`, and `refinement*.md` in the task directory
 - Check whether each `{file-stem}` was already published by its hidden marker; publish only missing artifacts
 - Backfill only appends missing comments; never delete or reorder existing comments
+- Resolve `{agent}` for backfilled comments in this order:
+  1. Match the artifact filename in Activity Log (for example `→ analysis.md`) and extract the executor from `by {agent}`
+  2. If no match is found, fall back to `assigned_to` in task.md frontmatter
+  3. If `assigned_to` is also unavailable, use the current backfilling agent
 - Derive the previous and next neighbors from Activity Log order and add this note below the title:
 
 ```markdown

package/templates/.agents/rules/issue-sync.zh-CN.md

@@ -88,12 +88,16 @@ gh api "repos/{owner}/{repo}/issues/{issue-number}/comments" \
 <!-- sync-issue:{task-id}:{file-stem} -->
 ## {artifact-title}
 
+> **{agent}** · {task-id}
+
 {artifact body}
 
 ---
-*由 AI 自动生成 · 内部追踪：{task-id}*
+*由 {agent} 自动生成 · 内部追踪：{task-id}*
 ```
 
+其中 `{agent}` 使用当前执行该技能的 AI 代理名称（如 `claude`、`codex`、`gemini`）。
+
 `summary` 评论需要额外处理：
 - 先查找已有 `<!-- sync-issue:{task-id}:summary -->` 评论的 ID
 - 不存在则创建
@@ -133,6 +137,8 @@ task.md 评论格式：
 <!-- sync-issue:{task-id}:task -->
 ## 任务文件
 
+> **{agent}** · {task-id}
+
 <details><summary>元数据 (frontmatter)</summary>
 
 ​```yaml
@@ -146,7 +152,7 @@ task.md 评论格式：
 {task.md body after frontmatter}
 
 ---
-*由 AI 自动生成 · 内部追踪：{task-id}*
+*由 {agent} 自动生成 · 内部追踪：{task-id}*
 ```
 
 还原时，从 `<details>` 块中提取 frontmatter，与正文拼合恢复为原始 `task.md`。
@@ -159,6 +165,10 @@ task.md 评论格式：
 - 扫描任务目录中的 `task.md`、`analysis*.md`、`plan*.md`、`implementation*.md`、`review*.md`、`refinement*.md`
 - 对每个 `{file-stem}` 用隐藏标记检查是否已发布；未发布则补发，已发布则跳过
 - 补发只追加缺失评论，不删除或重排已有评论
+- 补发评论的 `{agent}` 按以下顺序确定：
+  1. 从 Activity Log 中匹配对应产物文件名（如 `→ analysis.md`），提取 `by {agent}` 中的执行者
+  2. 若未匹配到，则回退到 task.md frontmatter 的 `assigned_to`
+  3. 若 `assigned_to` 也不可用，则使用当前执行补发的 agent
 - 位置说明从 Activity Log 推导时间线中的前后邻居，并加在评论标题下方：
 
 ```markdown

package/templates/.agents/rules/task-management.md

@@ -0,0 +1,28 @@
+# General Rules - Task Management
+
+## Task Intent Detection
+
+Map user intent to the corresponding workflow command:
+- "analyze issue #123" -> `import-issue`
+- "analyze task TASK-20260306-143022" -> `analyze-task`
+- "design a plan" -> `plan-task`
+- "implement" or "build" -> `implement-task`
+- "review" -> `review-task`
+- "fix review feedback" -> `refine-task`
+
+## Task State Management
+
+- Update the corresponding `task.md` immediately after every workflow command
+- At minimum, synchronize `current_step`, `updated_at`, `assigned_to`, and the current-round artifact reference
+- Activity Log entries are append-only and must never overwrite history
+
+## Required State Updates by Command
+
+- `import-issue`: update `current_step`, `updated_at`, `assigned_to`
+- `analyze-task`: update `current_step`, `updated_at`, `assigned_to`
+- `plan-task`: update `current_step`, `updated_at`
+- `implement-task`: update `current_step`, `updated_at`
+- `review-task`: update `current_step`, `updated_at`
+- `refine-task`: update `current_step`, `updated_at`
+- `complete-task`: update `status`, `completed_at`, `updated_at`
+- `block-task`: update `status`, `blocked_at`, `blocked_reason`

package/templates/.agents/rules/task-management.zh-CN.md

@@ -0,0 +1,28 @@
+# 通用规则 - 任务管理
+
+## 任务语义识别
+
+根据用户意图自动映射到对应工作流命令：
+- “分析 issue #123” -> `import-issue`
+- “分析任务 TASK-20260306-143022” -> `analyze-task`
+- “设计方案” -> `plan-task`
+- “实施/实现” -> `implement-task`
+- “审查” -> `review-task`
+- “修复审查问题” -> `refine-task`
+
+## 任务状态管理
+
+- 每次执行工作流命令后，必须立即更新对应任务的 `task.md`
+- 至少同步 `current_step`、`updated_at`、`assigned_to`，以及本轮产物引用
+- Activity Log 只能追加，不能覆盖历史记录
+
+## 常见命令的状态更新要求
+
+- `import-issue`：更新 `current_step`、`updated_at`、`assigned_to`
+- `analyze-task`：更新 `current_step`、`updated_at`、`assigned_to`
+- `plan-task`：更新 `current_step`、`updated_at`
+- `implement-task`：更新 `current_step`、`updated_at`
+- `review-task`：更新 `current_step`、`updated_at`
+- `refine-task`：更新 `current_step`、`updated_at`
+- `complete-task`：更新 `status`、`completed_at`、`updated_at`
+- `block-task`：更新 `status`、`blocked_at`、`blocked_reason`

package/templates/.agents/skills/update-agent-infra/scripts/sync-templates.js

@@ -57,7 +57,7 @@ const DEFAULTS = {
   }
 };
 
-const INSTALLER_VERSION = "v0.4.4";
+const INSTALLER_VERSION = "v0.4.5";
 
 function norm(p) { return p.replace(/\\/g, '/'); }