@fitlab-ai/agent-infra 0.5.3 → 0.5.5

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

@@ -54,7 +54,7 @@ git rev-parse v<prev-version>
 - 后续步骤 7 生成发布说明时，**必须**同时参考步骤 3 的历史格式风格和完整分类清单，保持版本间的一致性
 - 如果没有历史发布说明，则使用步骤 7 中定义的默认格式
 
-### 4. 收集已合并的 PR
+### 4. 收集已合并的 PR 与贡献者
 
 获取标签之间的日期范围，然后查询已合并的 PR：
 
@@ -71,6 +71,17 @@ git log v<version> --format=%aI -1
 git log v<prev-version>..v<version> --format="%H %s" --no-merges
 ```
 
+从 commit `Co-authored-by` trailer 中收集协作贡献者：
+
+```bash
+git log v<prev-version>..v<version> \
+  --no-merges \
+  --format='%(trailers:key=Co-authored-by,valueonly,unfold)' \
+  | grep -v '^$' | sort | uniq -c | sort -rn
+```
+
+输出每行一个 `Name <email>`（`uniq -c` 给出该身份在范围内作为 co-author 的 commit 数）。
+
 ### 5. 收集关联 Issue
 
 从每个 PR body 中提取关联的 Issue：
@@ -115,7 +126,21 @@ git log v<prev-version>..v<version> --format="%H %s" --no-merges
 1. 条目格式：`- [scope] Description by @author in [#N](url)`
 2. Issue + PR：`in [#Issue](url) and [#PR](url)`
 3. 描述：使用 PR 标题，移除 `type(scope):` 前缀，首字母大写
-4. 贡献者：去重，按贡献数量降序排列
+4. **贡献者搜集**：
+   - **数据源**：
+     - PR author：来自步骤 4 的 `gh pr list --json author`
+     - Commit co-authors：来自步骤 4 的 `git log ... --format='%(trailers:key=Co-authored-by,valueonly,unfold)'`
+   - **贡献数定义**：`该人的 PR 数 + 该人作为 co-author 的 commit 数`（同一身份跨来源合并计数）
+   - **Name → `@login` 映射**：
+     - `Co-authored-by` 原始格式为 `Name <email>`，需要推断对应的 GitHub `@login`
+     - 优先从 email 提取：匹配 `(\d+\+)?(\S+?)@users\.noreply\.github\.com` 时，取第二个捕获组并转为小写；该正则同时覆盖 `{id}+{login}@users.noreply.github.com` 与 `{login}@users.noreply.github.com`
+     - 否则按 Name 启发式：取首个空格前的 token 并转为小写（例如 `Claude Opus 4.6 (1M context)` → `@claude`、`Codex` → `@codex`、`Gemini` → `@gemini`）
+     - 已出现在 PR author 列表中的 login，必须按该 login 合并计数，避免把 `Claude` 和 `@claude` 拆成两个条目
+     - 同一 login 的所有 Name 变体都必须归并后再计数与排序；例如 `Claude` 与 `Claude Opus 4.6 (1M context)` 都映射到 `@claude` 时，应先合并为同一个贡献者
+     - Bot 身份保留原样（如 `dependabot[bot]`）
+     - 若仍无法可靠确定 login，则输出 `@{Name 首 token 小写}`，并在 `Contributors` 段落下追加 `<!-- TODO(reviewer): 确认 {原始 Name <email>} 的 GitHub login -->`
+   - **排序**：按贡献数降序；贡献数相同时按 login 字典序
+   - **去重**：以最终映射后的 `@login` 为键
 5. 空部分：省略没有条目的部分
 
 ### 8. 展示并确认

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

@@ -20,6 +20,6 @@
       "expected_action_pattern": "Task Created",
       "freshness_minutes": 30
     },
-    "github-sync": null
+    "platform-sync": null
   }
 }

package/templates/.agents/skills/implement-task/SKILL.en.md

@@ -39,7 +39,7 @@ After this step, write the final branch name back to `task.md`.
 
 ### 3. Narrow the Milestone
 
-If task.md contains a valid `issue_number`, read `.agents/rules/milestone-inference.md` and follow "Phase 2: `implement-task`" to narrow the Issue milestone before implementation starts.
+If task.md contains a valid `issue_number`, read `.agents/rules/issue-sync.md` first to complete upstream repository detection plus permission detection; then read `.agents/rules/milestone-inference.md` and follow "Phase 2: `implement-task`" to narrow the Issue milestone before implementation starts; if `has_triage=false`, keep the current milestone unchanged.
 
 ### 4. Determine the Input Plan and Implementation Round
 
@@ -93,9 +93,9 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - append:
   `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
 
-If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure; read `.agents/rules/issue-sync.md` first):
-- Set `status: in-progress` and refine `in:` labels from the branch diff by following `.agents/rules/issue-sync.md` (add/remove when a mapping exists, add-only when it does not)
-- Sync checked `## Requirements` items to the Issue body and publish the `{implementation-artifact}` comment
+If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure; read `.agents/rules/issue-sync.md` first and complete upstream repository detection plus permission detection):
+- Set `status: in-progress` by following issue-sync.md
+- Publish the `{implementation-artifact}` comment
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
 
 ### 10. Verification Gate

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

@@ -39,7 +39,7 @@ description: "根据技术方案实施任务并输出报告"
 
 ### 3. 收窄里程碑
 
-如果 task.md 中存在有效的 `issue_number`，按 `.agents/rules/milestone-inference.md` 的「阶段 2：`implement-task`」收窄 Issue milestone。执行前先读取该文件。
+如果 task.md 中存在有效的 `issue_number`，执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测；再读取 `.agents/rules/milestone-inference.md`，按其中的「阶段 2：`implement-task`」收窄 Issue milestone；如果 `has_triage=false`，则保持原 milestone 不变。
 
 ### 4. 确定输入方案与实现轮次
 
@@ -93,9 +93,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - 追加：
   `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
 
-如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续；执行前先读取 `.agents/rules/issue-sync.md`）：
-- 设置 `status: in-progress`，并按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则，基于分支改动精修 `in:` label（有映射时可增可删，无映射时仅补充）
-- 同步 `## 需求` 中已勾选项到 Issue body，并发布 `{implementation-artifact}` 评论
+如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续；执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测）：
+- 按 issue-sync.md 设置 `status: in-progress`
+- 发布 `{implementation-artifact}` 评论
 - 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
 
 ### 10. 完成校验

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

@@ -29,13 +29,12 @@
       "expected_action_pattern": "Implementation \\(Round \\d+\\)",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_status_label": "status: in-progress",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,
-      "sync_checked_requirements": true,
       "verify_issue_type": true,
       "verify_milestone": true
     }

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

@@ -19,6 +19,6 @@
       "expected_action_pattern": "Import Code Scanning Alert",
       "freshness_minutes": 30
     },
-    "github-sync": null
+    "platform-sync": null
   }
 }

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

@@ -19,6 +19,6 @@
       "expected_action_pattern": "Import Dependabot Alert",
       "freshness_minutes": 30
     },
-    "github-sync": null
+    "platform-sync": null
   }
 }

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

@@ -17,7 +17,7 @@ Import the specified GitHub Issue and create a task. Argument: issue number.
 
 ### 1. Retrieve Issue Information
 
-Read `.agents/rules/issue-pr-commands.md` first, then use its "Read an Issue" command to load the Issue data.
+Read `.agents/rules/issue-pr-commands.md` first, follow its prerequisite steps to complete authentication and code-hosting platform detection, then load the Issue data with its "Read an Issue" command.
 
 Extract: issue number, title, description, and labels.
 Use the Issue title as-is for the task title (preserve the Issue's original language).

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

@@ -17,7 +17,7 @@ description: "从 GitHub Issue 导入并创建任务"
 
 ### 1. 获取 Issue 信息
 
-执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的 “读取 Issue” 命令获取 Issue 信息。
+执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的前置步骤完成认证和代码托管平台检测；随后按其中的 “读取 Issue” 命令获取 Issue 信息。
 
 提取：issue 编号、标题、描述、标签。
 任务标题直接使用 Issue 的原始标题（保持 Issue 标题的原始语言）。

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

@@ -20,7 +20,7 @@
       "expected_action_pattern": "Import Issue",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "issue_must_exist": true
     }

package/templates/.agents/skills/plan-task/SKILL.en.md

@@ -97,8 +97,8 @@ Update `.agents/workspace/active/{task-id}/task.md`:
   ```
 
 If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):
-- Read `.agents/rules/issue-sync.md` before syncing
-- Set `status: pending-design-work`
+- Read `.agents/rules/issue-sync.md` before syncing, and complete upstream repository detection plus permission detection
+- Set `status: pending-design-work` by following issue-sync.md
 - Publish the `{plan-artifact}` comment
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
 

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

@@ -97,8 +97,8 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   ```
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
-- 执行前先读取 `.agents/rules/issue-sync.md`
-- 设置 `status: pending-design-work`
+- 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
+- 按 issue-sync.md 设置 `status: pending-design-work`
 - 发布 `{plan-artifact}` 评论
 - 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
 

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

@@ -31,7 +31,7 @@
       "expected_action_pattern": "Technical Design \\(Round \\d+\\)",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_status_label": "status: pending-design-work",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",

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

@@ -60,10 +60,8 @@ Update task.md:
   `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
 If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):
-- Read `.agents/rules/issue-sync.md` before syncing
-- Set `status: in-progress`
-- Refine `in:` labels from the branch diff by following `.agents/rules/issue-sync.md` (add/remove when a mapping exists, add-only when it does not)
-- Sync checked `## Requirements` items to the Issue body
+- Read `.agents/rules/issue-sync.md` before syncing, and complete upstream repository detection plus permission detection
+- Set `status: in-progress` by following issue-sync.md
 - Publish the `{refinement-artifact}` comment
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
 

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

@@ -60,10 +60,8 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
-- 执行前先读取 `.agents/rules/issue-sync.md`
-- 设置 `status: in-progress`
-- 按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则，基于分支改动精修 `in:` label（有映射时可增可删，无映射时仅补充）
-- 同步 `## 需求` 中已勾选项到 Issue body
+- 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
+- 按 issue-sync.md 设置 `status: in-progress`
 - 发布 `{refinement-artifact}` 评论
 - 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
 

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

@@ -25,13 +25,12 @@
       "expected_action_pattern": "Refinement \\(Round \\d+, for .+\\)",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_status_label": "status: in-progress",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,
-      "sync_checked_requirements": true,
       "verify_issue_type": true,
       "verify_milestone": true
     }

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

@@ -11,7 +11,7 @@ Reformat the title of the specified Issue or PR to Conventional Commits format b
 
 ### 1. Identify Target and Fetch Information
 
-Read `.agents/rules/issue-pr-commands.md` before this step.
+Read `.agents/rules/issue-pr-commands.md` before this step, and follow its prerequisite steps to complete authentication and code-hosting platform detection.
 
 Try to determine if the ID is an Issue or PR:
 - first fetch Issue data by following the "Read an Issue" command in the rule file
@@ -58,6 +58,8 @@ If the user confirms:
 - for an Issue, update the title by following the "Update Issues" command in `.agents/rules/issue-pr-commands.md`
 - for a PR, update the title by following the "Update PRs" command in `.agents/rules/issue-pr-commands.md`
 
+Title changes require write permission. Follow the permission-degradation rules in `.agents/rules/issue-pr-commands.md` and `.agents/rules/issue-sync.md`; if permission is unavailable, skip the change and inform the user.
+
 ### 5. 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.
@@ -66,6 +68,8 @@ If the skill updated an Issue title, explain that no extra sync command is requi
 
 If the skill updated a PR title, explain that `create-pr` now publishes the reviewer summary inline, so no extra sync command is needed; continue with the workflow skill that matches the task's current stage.
 
+If title modification was skipped due to insufficient permissions, additionally remind the user that the suggested title can still be applied manually on the code-hosting platform page.
+
 ## Advantages
 
 This skill:

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

@@ -11,7 +11,7 @@ description: "重构 Issue/PR 标题为 Conventional Commits 格式"
 
 ### 1. 识别目标并获取信息
 
-执行前先读取 `.agents/rules/issue-pr-commands.md`。
+执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的前置步骤完成认证和代码托管平台检测。
 
 尝试判断 ID 是 Issue 还是 PR：
 - 先按规则文件中的“读取 Issue”命令获取 Issue 信息
@@ -58,6 +58,8 @@ Issue/PR #{id} 分析结果：
 - 对于 Issue：按 `.agents/rules/issue-pr-commands.md` 中的 “Issue 更新” 命令设置标题
 - 对于 PR：按 `.agents/rules/issue-pr-commands.md` 中的 “PR 更新” 命令设置标题
 
+标题修改需要写权限，按 `.agents/rules/issue-pr-commands.md` 与 `.agents/rules/issue-sync.md` 中的权限降级规则执行；无权限时跳过修改操作并告知用户。
+
 ### 5. 告知用户
 
 > **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
@@ -66,6 +68,8 @@ Issue/PR #{id} 分析结果：
 
 如果修改了 PR 标题，提示 `create-pr` 已内联发布 reviewer 摘要，无需额外同步命令；后续按任务当前阶段继续执行对应工作流技能。
 
+如果因权限不足跳过了标题修改，额外提示用户建议标题仍可手动应用到代码托管平台页面。
+
 ## 优势
 
 本技能的优势：

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

@@ -19,6 +19,6 @@
       "expected_action_pattern": "Restore Task",
       "freshness_minutes": 30
     },
-    "github-sync": null
+    "platform-sync": null
   }
 }

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

@@ -54,8 +54,8 @@ Update task.md and append:
 `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
 
 If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):
-- Read `.agents/rules/issue-sync.md` before syncing
-- Set `status: in-progress`
+- Read `.agents/rules/issue-sync.md` before syncing, and complete upstream repository detection plus permission detection
+- Set `status: in-progress` by following issue-sync.md
 - Publish the `{review-artifact}` comment
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
 

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

@@ -54,8 +54,8 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
-- 执行前先读取 `.agents/rules/issue-sync.md`
-- 设置 `status: in-progress`
+- 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
+- 按 issue-sync.md 设置 `status: in-progress`
 - 发布 `{review-artifact}` 评论
 - 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
 

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

@@ -29,7 +29,7 @@
       "expected_action_pattern": "Code Review \\(Round \\d+\\)",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_status_label": "status: in-progress",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",

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

@@ -56,6 +56,7 @@ const DEFAULTS = {
       ".claude/hooks/",
       ".gemini/commands/",
       ".github/hooks/check-version-format.sh",
+      ".github/scripts/",
       ".opencode/commands/"
     ],
     "merged": [
@@ -76,7 +77,7 @@ const DEFAULTS = {
   }
 };
 
-const INSTALLER_VERSION = "v0.5.3";
+const INSTALLER_VERSION = "v0.5.5";
 const PACKAGE_NAME = '@fitlab-ai/agent-infra';
 // Add a new identifier here only after shipping matching .{platform}. template variants.
 const KNOWN_PLATFORMS = new Set(['github']);

package/templates/.github/scripts/sync-labels-to-set.sh

@@ -0,0 +1,110 @@
+#!/bin/sh
+# Ensure the labels matching --prefix on an issue or PR equal the set passed via
+# repeated --target flags (0, 1, or N labels).
+# Algorithm must stay in sync with .agents/rules/issue-sync.md.
+
+set -e
+
+usage() {
+  printf 'Usage: %s --repo <owner/repo> (--issue <number> | --pr <number>) --prefix <prefix> [--target <label> ...]\n' "$0" >&2
+  exit 1
+}
+
+append_target() {
+  if [ -n "$targets" ]; then
+    targets=$(printf '%s\n%s' "$targets" "$1")
+  else
+    targets=$1
+  fi
+}
+
+repo=""
+number=""
+kind=""
+prefix=""
+targets=""
+
+while [ $# -gt 0 ]; do
+  case "$1" in
+    --repo)
+      [ $# -ge 2 ] || usage
+      repo=$2
+      shift 2
+      ;;
+    --issue)
+      [ $# -ge 2 ] || usage
+      [ -z "$kind" ] || usage
+      kind="issue"
+      number=$2
+      shift 2
+      ;;
+    --pr)
+      [ $# -ge 2 ] || usage
+      [ -z "$kind" ] || usage
+      kind="pr"
+      number=$2
+      shift 2
+      ;;
+    --prefix)
+      [ $# -ge 2 ] || usage
+      prefix=$2
+      shift 2
+      ;;
+    --target)
+      [ $# -ge 2 ] || usage
+      append_target "$2"
+      shift 2
+      ;;
+    *)
+      printf 'Unknown argument: %s\n' "$1" >&2
+      usage
+      ;;
+  esac
+done
+
+[ -n "$repo" ] || usage
+[ -n "$number" ] || usage
+[ -n "$kind" ] || usage
+[ -n "$prefix" ] || usage
+
+while IFS= read -r label; do
+  [ -z "$label" ] && continue
+  case "$label" in
+    "$prefix"*) ;;
+    *)
+      printf 'Target "%s" must start with prefix "%s"\n' "$label" "$prefix" >&2
+      exit 1
+      ;;
+  esac
+done <<EOF
+$targets
+EOF
+
+current_labels=$(gh "$kind" view "$number" \
+  --repo "$repo" \
+  --json labels --jq ".labels[].name | select(startswith(\"$prefix\"))" \
+  2>/dev/null || true)
+
+while IFS= read -r label; do
+  [ -z "$label" ] && continue
+  if ! printf '%s\n' "$targets" | grep -qxF "$label"; then
+    gh "$kind" edit "$number" \
+      --repo "$repo" \
+      --remove-label "$label" \
+      2>/dev/null || true
+  fi
+done <<EOF
+$current_labels
+EOF
+
+while IFS= read -r label; do
+  [ -z "$label" ] && continue
+  if ! printf '%s\n' "$current_labels" | grep -qxF "$label"; then
+    gh "$kind" edit "$number" \
+      --repo "$repo" \
+      --add-label "$label" \
+      2>/dev/null || true
+  fi
+done <<EOF
+$targets
+EOF

package/templates/.github/workflows/metadata-sync.yml

@@ -0,0 +1,118 @@
+name: Metadata Sync
+
+on:
+  issue_comment:
+    types: [created, edited]
+
+permissions:
+  issues: write
+
+jobs:
+  sync-metadata:
+    runs-on: ubuntu-latest
+    if: ${{ !github.event.issue.pull_request }}
+    steps:
+      - name: Extract metadata from task comment
+        id: metadata
+        run: |
+          body=$(jq -r '.comment.body' "$GITHUB_EVENT_PATH")
+          if ! printf '%s' "$body" | grep -qE '<!-- sync-issue:TASK-[0-9]{8}-[0-9]{6}:task -->'; then
+            printf 'is_task_comment=false\n' >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          frontmatter=$(printf '%s\n' "$body" \
+            | tr -d '\r' \
+            | awk '
+                BEGIN { capture = 0; separators = 0 }
+                $0 == "---" {
+                  separators += 1
+                  if (separators == 1) {
+                    capture = 1
+                    next
+                  }
+                  if (separators == 2) {
+                    exit
+                  }
+                }
+                capture { print }
+              ')
+
+          type=$(printf '%s\n' "$frontmatter" \
+            | sed -n 's/^type:[[:space:]]*//p' \
+            | head -n 1 \
+            | sed 's/[[:space:]]*#.*$//' \
+            | sed 's/^[[:space:]]*//; s/[[:space:]]*$//' \
+            | tr '[:upper:]' '[:lower:]')
+
+          milestone=$(printf '%s\n' "$frontmatter" \
+            | sed -n 's/^milestone:[[:space:]]*//p' \
+            | head -n 1 \
+            | sed 's/^[[:space:]]*//; s/[[:space:]]*$//')
+
+          printf 'is_task_comment=true\n' >> "$GITHUB_OUTPUT"
+          printf 'type=%s\n' "$type" >> "$GITHUB_OUTPUT"
+          printf 'milestone=%s\n' "$milestone" >> "$GITHUB_OUTPUT"
+
+      - name: Checkout shared scripts
+        if: steps.metadata.outputs.is_task_comment == 'true' && steps.metadata.outputs.type != ''
+        uses: actions/checkout@v4
+        with:
+          sparse-checkout: .github/scripts
+          sparse-checkout-cone-mode: false
+
+      - name: Sync type label
+        if: steps.metadata.outputs.is_task_comment == 'true' && steps.metadata.outputs.type != ''
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          TYPE: ${{ steps.metadata.outputs.type }}
+        run: |
+          case "$TYPE" in
+            bug|bugfix)                       TYPE_LABEL="type: bug" ;;
+            feature)                          TYPE_LABEL="type: feature" ;;
+            enhancement|refactor|refactoring) TYPE_LABEL="type: enhancement" ;;
+            docs|documentation)               TYPE_LABEL="type: documentation" ;;
+            dependency-upgrade)               TYPE_LABEL="type: dependency-upgrade" ;;
+            task|chore)                       TYPE_LABEL="type: task" ;;
+            *)                                TYPE_LABEL="" ;;
+          esac
+
+          if [ -n "$TYPE_LABEL" ]; then
+            .github/scripts/sync-labels-to-set.sh \
+              --repo "$GITHUB_REPOSITORY" \
+              --issue "$ISSUE_NUMBER" \
+              --prefix "type:" \
+              --target "$TYPE_LABEL"
+          fi
+
+      - name: Sync milestone
+        if: steps.metadata.outputs.is_task_comment == 'true' && steps.metadata.outputs.milestone != ''
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          MILESTONE: ${{ steps.metadata.outputs.milestone }}
+        run: |
+          gh issue edit "$ISSUE_NUMBER" \
+            --repo "$GITHUB_REPOSITORY" \
+            --milestone "$MILESTONE" \
+            2>/dev/null || true
+
+      - name: Sync issue type
+        if: steps.metadata.outputs.is_task_comment == 'true' && steps.metadata.outputs.type != ''
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          TYPE: ${{ steps.metadata.outputs.type }}
+        run: |
+          case "$TYPE" in
+            bug|bugfix)          ISSUE_TYPE="Bug" ;;
+            feature|enhancement) ISSUE_TYPE="Feature" ;;
+            *)                   ISSUE_TYPE="Task" ;;
+          esac
+
+          gh api "repos/$GITHUB_REPOSITORY/issues/$ISSUE_NUMBER" \
+            -X PATCH \
+            -f type="$ISSUE_TYPE" \
+            --silent \
+            2>/dev/null || true