@fitlab-ai/agent-infra 0.4.5 → 0.5.1

package/templates/.agents/skills/commit/reference/pr-summary-sync.md

@@ -0,0 +1,21 @@
+# Commit-Stage PR Summary Sync
+
+> For the full aggregation rules, hidden marker, comment body template, PATCH/POST flow, shell safety constraints, and error handling, read `.agents/rules/pr-sync.md` before this step.
+
+## Trigger Conditions
+
+Run this step only when both conditions are true:
+- `{task-id}` is valid
+- `task.md` frontmatter contains a valid `pr_number`
+
+If either condition is missing, skip PR summary sync and continue to verification.
+
+## Execution Notes
+
+- Generate or update the `<!-- sync-pr:{task-id}:summary -->` comment with the canonical template from `.agents/rules/pr-sync.md`
+- In this skill, PR summary sync failures are warnings only and must not block a completed `git commit`
+- If the summary body is unchanged, treat it as `summary skipped (no diff)`
+
+## Result Reporting
+
+Reuse the normalized result string from `.agents/rules/pr-sync.md` in this skill's user output or Activity Log.

package/templates/.agents/skills/commit/reference/pr-summary-sync.zh-CN.md

@@ -0,0 +1,21 @@
+# Commit 阶段 PR 摘要同步
+
+> 详细聚合规则、隐藏标记、评论体模板、PATCH/POST 流程、Shell 安全约束和错误处理见 `.agents/rules/pr-sync.md`。执行本步骤前先读取该 rule。
+
+## 触发条件
+
+仅当以下条件同时满足时执行：
+- `{task-id}` 有效
+- `task.md` frontmatter 中存在有效 `pr_number`
+
+任一条件不满足时，跳过 PR 摘要同步并继续后续校验。
+
+## 执行要求
+
+- 按 `.agents/rules/pr-sync.md` 中的唯一权威模板生成或更新 `<!-- sync-pr:{task-id}:summary -->` 评论
+- 在本 skill 中，PR 摘要同步失败只记为警告，不阻塞已完成的 `git commit`
+- 如果摘要正文无变化，按 `summary skipped (no diff)` 处理
+
+## 结果回传
+
+将 `.agents/rules/pr-sync.md` 中的结果回传字符串用于当前 skill 的用户输出或 Activity Log 复用。

package/templates/.agents/skills/commit/reference/task-status-update.md

@@ -86,3 +86,5 @@ Next step - create Pull Request:
   - Gemini CLI: /agent-infra:create-pr {task-id}
   - Codex CLI: $create-pr {task-id}
 ```
+
+> Note: beyond the four cases, if `task.md` contains a valid `pr_number`, the commit skill must sync the PR summary via `reference/pr-summary-sync.md` before entering the verification gate.

package/templates/.agents/skills/commit/reference/task-status-update.zh-CN.md

@@ -86,3 +86,5 @@ date "+%Y-%m-%d %H:%M:%S"
   - Gemini CLI: /agent-infra:create-pr {task-id}
   - Codex CLI: $create-pr {task-id}
 ```
+
+> 注意：四个场景之外，只要 `task.md` 中存在有效 `pr_number`，commit 技能必须先按 `reference/pr-summary-sync.md` 同步 PR 摘要，再进入完成校验。

package/templates/.agents/skills/create-pr/SKILL.md

@@ -58,11 +58,12 @@ Read the latest context artifacts when they exist: `plan.md` / `plan-r{N}.md`, `
 
 Aggregate a reviewer-facing summary from those artifacts and maintain a single idempotent summary comment via the hidden marker.
 
-> Hidden marker handling, idempotent summary updates, review-history structure, and comment creation/update rules live in `reference/comment-publish.md`. Read `reference/comment-publish.md` before publishing the summary.
+> Hidden marker handling, idempotent summary updates, review-history structure, and comment creation/update rules live in `reference/comment-publish.md` (which in turn points to `.agents/rules/pr-sync.md`). Read `reference/comment-publish.md` before publishing the summary.
 >
 > **Shell safety rules** (required before publishing the comment):
 > 1. Replace `{comment-body}` with the actual inline text. Read files first, then paste the full content into the heredoc body. Do **not** use `$(cat ...)`, `$(< ...)`, `$(...)`, or `${...}` inside `<<'EOF'`.
 > 2. Do **not** use `echo` when constructing strings that contain `<!-- -->`. Use `cat <<'EOF'` heredoc or `printf '%s\n'` instead.
+> 3. The same constraints are restated in `.agents/rules/pr-sync.md`; once that rule is loaded, do not duplicate another copy of the template rules.
 
 ### 8. Update Task Status
 

package/templates/.agents/skills/create-pr/SKILL.zh-CN.md

@@ -58,11 +58,12 @@ description: "创建 Pull Request 到目标分支"
 
 基于这些产物聚合 reviewer 摘要，并使用隐藏标记维护唯一且幂等的摘要评论。
 
-> 隐藏标记、幂等 summary 评论更新、review history 格式，以及评论创建/更新规则见 `reference/comment-publish.md`。发布摘要前先读取 `reference/comment-publish.md`。
+> 隐藏标记、幂等 summary 评论更新、review history 格式，以及评论创建/更新规则见 `reference/comment-publish.md`（其内联引用 `.agents/rules/pr-sync.md`）。发布摘要前先读取 `reference/comment-publish.md`。
 >
 > **Shell 安全规则**（发布评论前必读）：
 > 1. `{comment-body}` 必须替换为**实际的内联文本**。先读取文件，再将全文粘贴到 heredoc body 中。**禁止**在 `<<'EOF'` 内部使用 `$(cat ...)`、`$(< ...)`、`$(...)`、`${...}`。
 > 2. 构造含 `<!-- -->` 的字符串时，**禁止使用 `echo`**。统一使用 `cat <<'EOF'` heredoc 或 `printf '%s\n'` 构造。
+> 3. 同样的安全约束已在 `.agents/rules/pr-sync.md` 中重述，调用该 rule 后无需重复补充另一份模板规则。
 
 ### 8. 更新任务状态
 

package/templates/.agents/skills/create-pr/reference/comment-publish.md

@@ -2,81 +2,14 @@
 
 Read this file before creating or updating the single reviewer-facing PR summary comment from `create-pr`.
 
-## Create or Update the Single Idempotent Review Summary
+> For the full aggregation rules, hidden marker, comment body template, PATCH/POST flow, shell safety constraints, and error handling, read `.agents/rules/pr-sync.md` before this step.
 
-Use the hidden marker:
+## Execution Notes
 
-```html
-<!-- sync-pr:{task-id}:summary -->
-```
+- Generate or update the `<!-- sync-pr:{task-id}:summary -->` comment with the canonical template from `.agents/rules/pr-sync.md`
+- When a matching summary comment already exists, PATCH only when the body changed; otherwise skip the write
+- In this skill, summary sync failures follow the existing `create-pr` error handling and must not roll back an already-created PR
 
-Fetch existing comments through the Issues comments API, not a separate PR comment API.
+## Result Reporting
 
-Recommended summary sections:
-- `## Review Summary`
-- `### Key Technical Decisions`
-- `### Review History`
-- `### Test Results`
-
-Summary content rules:
-- write for reviewers, not for end users
-- do not restate the raw file diff
-- extract 2-4 self-contained technical decisions from `plan.md`
-- avoid internal shorthand such as `Plan A/B`; each decision must make sense on its own
-- build a review-history table from `review.md`, `review-r{N}.md`, `refinement.md`, and `refinement-r{N}.md`
-- include test results from `implementation.md` or refinement artifacts
-
-Recommended review-history columns:
-- `Round`
-- `Verdict`
-- `Finding Counts`
-- `Fix Status`
-
-If a summary comment already exists:
-- update it only when the content changed
-- otherwise skip the write
-
-If no summary comment exists:
-- create one with the marker and the current summary body
-
-Update an existing comment with:
-
-```bash
-gh api "repos/$repo/issues/comments/{comment-id}" -X PATCH -f body="$(cat <<'EOF'
-{comment-body}
-EOF
-)"
-```
-
-Suggested summary body:
-
-```markdown
-<!-- sync-pr:{task-id}:summary -->
-## Review Summary
-
-> **{agent}** · {task-id}
-
-**Updated At**: {current-time}
-
-### Key Technical Decisions
-
-- {decision-1}
-- {decision-2}
-
-### Review History
-
-| Round | Verdict | Finding Counts | Fix Status |
-|-------|---------|----------------|------------|
-| Round 1 | Pending | N/A | N/A |
-
-### Test Results
-
-- {test-summary}
-
----
-*Generated by {agent} · Internal tracking: {task-id}*
-```
-
-## Return the Result
-
-Return the summary outcome as `summary created`, `summary updated`, or `summary skipped` so `create-pr` can reuse it in user output and the PR Created Activity Log.
+Reuse the normalized result string from `.agents/rules/pr-sync.md` in this skill's user output or `PR Created` Activity Log.

package/templates/.agents/skills/create-pr/reference/comment-publish.zh-CN.md

@@ -2,81 +2,14 @@
 
 在 `create-pr` 中创建或更新面向 reviewer 的唯一 PR 摘要评论之前先读取本文件。
 
-## 创建或更新唯一且幂等的审查摘要
+> 详细聚合规则、隐藏标记、评论体模板、PATCH/POST 流程、Shell 安全约束和错误处理见 `.agents/rules/pr-sync.md`。执行本步骤前先读取该 rule。
 
-使用如下隐藏标记：
+## 执行要求
 
-```html
-<!-- sync-pr:{task-id}:summary -->
-```
-
-已有评论必须通过 Issues comments API 获取，而不是单独的 PR comments API。
-
-推荐摘要章节：
-- `## 审查摘要`
-- `### 关键技术决策`
-- `### 审查历程`
-- `### 测试结果`
-
-摘要内容规则：
-- 面向 reviewer 编写，而不是面向终端用户
-- 不要简单复述原始文件 diff
-- 从 `plan.md` 中提取 2-4 条自包含的技术决策
-- 避免使用 `方案 A/B` 这类内部简称；每条决策都必须独立可读
-- 用 `review.md`、`review-r{N}.md`、`refinement.md` 和 `refinement-r{N}.md` 构建审查历程表
-- 包含来自 `implementation.md` 或修复产物中的测试结果
-
-推荐审查历程列：
-- `轮次`
-- `结论`
-- `问题统计`
-- `修复状态`
-
-如果摘要评论已经存在：
-- 只有内容发生变化时才更新
-- 否则跳过写入
-
-如果摘要评论不存在：
-- 使用隐藏标记和当前摘要正文创建一条新评论
-
-更新已有评论时，使用：
-
-```bash
-gh api "repos/$repo/issues/comments/{comment-id}" -X PATCH -f body="$(cat <<'EOF'
-{comment-body}
-EOF
-)"
-```
-
-建议摘要正文：
-
-```markdown
-<!-- sync-pr:{task-id}:summary -->
-## 审查摘要
-
-> **{agent}** · {task-id}
-
-**更新时间**：{当前时间}
-
-### 关键技术决策
-
-- {decision-1}
-- {decision-2}
-
-### 审查历程
-
-| 轮次 | 结论 | 问题统计 | 修复状态 |
-|------|------|----------|----------|
-| Round 1 | Pending | N/A | N/A |
-
-### 测试结果
-
-- {test-summary}
-
----
-*由 {agent} 自动生成 · 内部追踪：{task-id}*
-```
+- 按 `.agents/rules/pr-sync.md` 中的唯一权威模板生成或更新 `<!-- sync-pr:{task-id}:summary -->` 评论
+- PR 已存在同标记评论时，只在正文变化时 PATCH；否则跳过写入
+- 本 skill 中，摘要同步失败沿用 `create-pr` 的现有错误处理，不回滚已经创建的 PR
 
 ## 结果回传
 
-将摘要结果整理为 `summary created`、`summary updated` 或 `summary skipped`，供 `create-pr` 在用户输出和 PR Created Activity Log 中复用。
+将 `.agents/rules/pr-sync.md` 中的结果回传字符串用于当前 skill 的用户输出或 `PR Created` Activity Log 复用。

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

@@ -27,6 +27,10 @@ Extract from the natural-language description:
 - **Task title**: a concise title (maximum 50 characters), in the same language as the user's description - do not translate it to English or apply Conventional Commits formatting
 - **Task type**: `feature` | `bugfix` | `refactor` | `docs` | `chore` (infer from the description)
 - **Workflow**: `feature-development` | `bug-fix` | `refactoring` (infer from the type)
+- **Branch name**: format `<project>-<type>-<slug>`
+  - `<project>` comes from the `project` field in `.agents/.airc.json`
+  - `<type>` is the inferred task type
+  - `<slug>` is a kebab-case slug built from 3-6 English keywords extracted from the task title
 - **Detailed description**: the cleaned-up original user request
 
 If the description is unclear, **ask the user to clarify first**.
@@ -64,6 +68,7 @@ Task metadata (`task.md` YAML front matter):
 ```yaml
 id: TASK-{yyyyMMdd-HHmmss}
 type: feature|bugfix|refactor|docs|chore
+branch: <project>-<type>-<slug>
 workflow: feature-development|bug-fix|refactoring
 status: active
 created_at: {yyyy-MM-dd HH:mm:ss}
@@ -87,6 +92,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
+- `## Context` -> `- **Branch**:`: update it to the generated branch name
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Task Created** by {agent} — Task created from description

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

@@ -27,6 +27,10 @@ description: "根据自然语言描述创建任务"
 - **任务标题**：简洁标题（最多 50 个字符），使用中文——不要翻译为英文，不要套用 Conventional Commits 格式
 - **任务类型**：`feature` | `bugfix` | `refactor` | `docs` | `chore`（从描述推断）
 - **工作流**：`feature-development` | `bug-fix` | `refactoring`（从类型推断）
+- **分支名**：格式 `<project>-<type>-<slug>`
+  - `<project>` 从 `.agents/.airc.json` 的 `project` 字段读取
+  - `<type>` 为推断出的任务类型
+  - `<slug>` 从任务标题提取 3-6 个英文关键词并转为 kebab-case
 - **详细描述**：整理后的用户原始描述
 
 如果描述不清晰，**先向用户确认**再继续。
@@ -64,6 +68,7 @@ date +%Y%m%d-%H%M%S
 ```yaml
 id: TASK-{yyyyMMdd-HHmmss}
 type: feature|bugfix|refactor|docs|chore
+branch: <project>-<type>-<slug>
 workflow: feature-development|bug-fix|refactoring
 status: active
 created_at: {yyyy-MM-dd HH:mm:ss}
@@ -87,6 +92,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - `current_step`：requirement-analysis
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
+- `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Task Created** by {agent} — Task created from description

package/templates/.agents/skills/create-task/config/verify.json

@@ -5,6 +5,7 @@
       "required_fields": [
         "id",
         "type",
+        "branch",
         "workflow",
         "status",
         "created_at",

package/templates/.agents/skills/import-issue/SKILL.md

@@ -44,6 +44,7 @@ Task metadata:
 id: TASK-{yyyyMMdd-HHmmss}
 issue_number: <issue-number>
 type: feature|bugfix|refactor|docs|chore
+branch: <project>-<type>-<slug>
 workflow: feature-development|bug-fix|refactoring
 status: active
 created_at: {yyyy-MM-dd HH:mm:ss}
@@ -65,6 +66,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
+- `## Context` -> `- **Branch**:`: update it to the generated branch name
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported

package/templates/.agents/skills/import-issue/SKILL.zh-CN.md

@@ -44,6 +44,7 @@ date +%Y%m%d-%H%M%S
 id: TASK-{yyyyMMdd-HHmmss}
 issue_number: <issue-number>
 type: feature|bugfix|refactor|docs|chore
+branch: <project>-<type>-<slug>
 workflow: feature-development|bug-fix|refactoring
 status: active
 created_at: {yyyy-MM-dd HH:mm:ss}
@@ -65,6 +66,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - `current_step`：requirement-analysis
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
+- `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported

package/templates/.agents/skills/import-issue/config/verify.json

@@ -5,6 +5,7 @@
       "required_fields": [
         "id",
         "type",
+        "branch",
         "workflow",
         "status",
         "created_at",

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

@@ -20,6 +20,23 @@ import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 
 const DEFAULTS = {
+  "sandbox": {
+    "runtimes": [
+      "node20"
+    ],
+    "tools": [
+      "claude-code",
+      "codex",
+      "opencode",
+      "gemini-cli"
+    ],
+    "dockerfile": null,
+    "vm": {
+      "cpu": null,
+      "memory": null,
+      "disk": null
+    }
+  },
   "labels": {
     "in": {}
   },
@@ -57,7 +74,7 @@ const DEFAULTS = {
   }
 };
 
-const INSTALLER_VERSION = "v0.4.5";
+const INSTALLER_VERSION = "v0.5.1";
 
 function norm(p) { return p.replace(/\\/g, '/'); }
 

package/templates/.agents/templates/task.md

@@ -1,12 +1,13 @@
 ---
 id: task-XXX
-type: feature          # feature | bugfix | refactor | docs | review
+type: feature                  # feature | bugfix | refactor | docs | review
+branch: ""                     # <project>-<type>-<slug>
 workflow: feature-development  # feature-development | bug-fix | code-review | refactoring
-status: open           # open | in-progress | review | blocked | completed
+status: open                   # open | in-progress | review | blocked | completed
 created_at: YYYY-MM-DD
 updated_at: YYYY-MM-DD
-current_step: analysis # analysis | design | implementation | review | fix | commit
-assigned_to: ""        # claude | codex | gemini | opencode | human
+current_step: analysis         # analysis | design | implementation | review | fix | commit
+assigned_to: ""                # claude | codex | gemini | opencode | human
 ---
 
 # Task: [Title]

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

@@ -1,12 +1,13 @@
 ---
 id: task-XXX
-type: feature          # feature | bugfix | refactor | docs | review
+type: feature                  # feature | bugfix | refactor | docs | review
+branch: ""                     # <project>-<type>-<slug>
 workflow: feature-development  # feature-development | bug-fix | code-review | refactoring
-status: open           # open | in-progress | review | blocked | completed
+status: open                   # open | in-progress | review | blocked | completed
 created_at: YYYY-MM-DD
 updated_at: YYYY-MM-DD
-current_step: analysis # analysis | design | implementation | review | fix | commit
-assigned_to: ""        # claude | codex | gemini | opencode | human
+current_step: analysis         # analysis | design | implementation | review | fix | commit
+assigned_to: ""                # claude | codex | gemini | opencode | human
 ---
 
 # 任务：[标题]