@fitlab-ai/agent-infra 0.5.3 → 0.5.5

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

@@ -119,8 +119,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 `{analysis-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/analyze-task/SKILL.zh-CN.md

@@ -119,8 +119,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`
 - 发布 `{analysis-artifact}` 评论
 - 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
 

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

@@ -30,7 +30,7 @@
       "expected_action_pattern": "Requirement Analysis \\(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/block-task/SKILL.en.md

@@ -70,9 +70,9 @@ ls .agents/workspace/blocked/{task-id}/task.md
 
 Check whether `task.md` includes a valid `issue_number`. If not, skip this step.
 
-> Status-label sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
+> Status-label sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing, and complete upstream repository detection plus permission detection.
 
-If a valid `issue_number` exists, set `status: blocked` directly.
+If a valid `issue_number` exists, set `status: blocked` by following issue-sync.md.
 
 ### 7. Verification Gate
 

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

@@ -70,9 +70,9 @@ ls .agents/workspace/blocked/{task-id}/task.md
 
 检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过。
 
-> Issue 同步的 status label 规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
+> Issue 同步的 status label 规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件，完成 upstream 仓库检测和权限检测。
 
-如果存在有效的 `issue_number`，直接设置 `status: blocked`。
+如果存在有效的 `issue_number`，按 issue-sync.md 设置 `status: blocked`。
 
 ### 7. 完成校验
 

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

@@ -20,7 +20,7 @@
       "expected_action_pattern": "Blocked",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_status_label": "status: blocked"
     }

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

@@ -1,6 +1,6 @@
 ---
 name: cancel-task
-description: "Cancel an unneeded task and archive it"
+description: "Cancel an unneeded task and move it"
 ---
 
 # Cancel Task
@@ -71,14 +71,14 @@ Confirm the task directory was moved successfully.
 
 Check whether `task.md` contains a valid `issue_number`. If not, skip this step.
 
-> Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
+> Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing, and complete upstream repository detection plus permission detection.
 > Read `.agents/rules/issue-pr-commands.md` before closing the Issue.
 
 If a valid `issue_number` exists:
-- Replace all `status:` labels with the label inferred in Step 2
-- Remove all `in:` labels
-- Remove the milestone
-- Remove all assignees
+- Replace all `status:` labels with the label inferred in Step 2 by following issue-sync.md
+- Remove all `in:` labels by following issue-sync.md
+- Remove the milestone by following issue-sync.md
+- Remove all assignees (skip directly when permission is insufficient; no fallback)
 - Publish a cancellation comment using the marker `<!-- sync-issue:{task-id}:cancel -->`
 - Create or update the `<!-- sync-issue:{task-id}:task -->` comment using the task-comment sync rules from `.agents/rules/issue-sync.md`
 - Close the Issue by following the "Close an Issue" command in `.agents/rules/issue-pr-commands.md`, using the fixed reason `not planned`

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

@@ -1,6 +1,6 @@
 ---
 name: cancel-task
-description: "取消不再需要的任务并归档"
+description: "取消不再需要的任务并转移"
 ---
 
 # 取消任务
@@ -71,14 +71,14 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过此步骤。
 
-> Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
+> Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件，完成 upstream 仓库检测和权限检测。
 > 关闭 Issue 前先读取 `.agents/rules/issue-pr-commands.md`。
 
 如果存在有效的 `issue_number`：
-- 替换所有 `status:` labels，并设置步骤 2 推断出的标签
-- 移除所有 `in:` labels
-- 移除 milestone
-- 移除全部 assignees
+- 按 issue-sync.md 替换所有 `status:` labels，并设置步骤 2 推断出的标签
+- 按 issue-sync.md 移除所有 `in:` labels
+- 按 issue-sync.md 移除 milestone
+- 移除全部 assignees（无权限时直接跳过，不做替代）
 - 发布取消评论，隐藏标记使用 `<!-- sync-issue:{task-id}:cancel -->`
 - 使用 `.agents/rules/issue-sync.md` 的 task.md 评论同步规则创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论
 - 关闭 Issue：按 `.agents/rules/issue-pr-commands.md` 中的“关闭 Issue”命令执行，关闭原因固定为 `not planned`

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

@@ -21,7 +21,7 @@
       "expected_action_pattern": "Cancelled",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:cancel -->",
       "verify_task_comment_content": true

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

@@ -52,15 +52,27 @@ Append the Commit Activity Log entry and choose exactly one next-step case:
 - ready for review -> `review-task {task-id}`
 - ready for PR -> `create-pr`
 
-## 6. Sync PR Summary When Applicable
+## 6. Sync Issue Metadata When Applicable
+
+When `{task-id}` exists and task.md contains a valid `issue_number`, sync the linked Issue `in:` labels and requirement checkboxes. Otherwise, skip this step.
+
+> Trigger conditions, `in:` label computation rules, and requirement-checkbox sync flow live in `reference/issue-metadata-sync.md`. Read that file before running this step.
+>
+> If this step touches the code-hosting platform, complete the prerequisite checks in `.agents/rules/issue-pr-commands.md` first.
+
+Failure handling matches "Update Task Status When Applicable": warn, but do **not** block an already completed `git commit`.
+
+## 7. Sync PR Summary When Applicable
 
 When `{task-id}` exists and task.md contains a valid `pr_number`, refresh the PR summary comment `<!-- sync-pr:{task-id}:summary -->` on the PR. Otherwise, skip this step.
 
 > The full trigger conditions, aggregation rules, PATCH/POST flow, shell-safety constraints, and error handling live in `reference/pr-summary-sync.md` (which in turn points to `.agents/rules/pr-sync.md`). Read `reference/pr-summary-sync.md` before executing this step.
+>
+> If this step touches the code-hosting platform, complete the prerequisite checks in `.agents/rules/issue-pr-commands.md` first so the runtime context required by `.agents/rules/pr-sync.md` is ready.
 
 Failure handling matches "Update Task Status When Applicable": warn, but do **not** block an already completed `git commit`.
 
-## 7. Verification Gate
+## 8. Verification Gate
 
 If this operation is associated with `{task-id}`, run the verification gate to confirm task metadata and sync state. If there is no task context, skip this step.
 

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

@@ -52,15 +52,27 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - 准备审查 -> `review-task {task-id}`
 - 准备创建 PR -> `create-pr`
 
-## 6. 同步 PR 摘要（按需）
+## 6. 同步 Issue 元数据（按需）
+
+当 `{task-id}` 存在且 task.md 包含有效 `issue_number` 时，同步 `in:` label 和需求复选框到关联 Issue；否则跳过。
+
+> 触发条件、`in:` label 计算规则和复选框同步流程见 `reference/issue-metadata-sync.md`。执行前先读取该文件。
+>
+> 如果本步骤会访问代码托管平台，则先按 `.agents/rules/issue-pr-commands.md` 完成前置检测。
+
+失败处理与「按需更新任务状态」一致：警告但**不**阻塞已完成的 `git commit`。
+
+## 7. 同步 PR 摘要（按需）
 
 当 `{task-id}` 存在且 task.md 包含有效 `pr_number` 时，刷新 PR 上的 `<!-- sync-pr:{task-id}:summary -->` 摘要评论；否则跳过。
 
 > 完整的触发条件、聚合规则、PATCH/POST 流程、Shell 安全约束和错误处理见 `reference/pr-summary-sync.md`（其内联引用 `.agents/rules/pr-sync.md`）。执行此步骤前先读取 `reference/pr-summary-sync.md`。
+>
+> 如果本步骤会访问代码托管平台，则先按 `.agents/rules/issue-pr-commands.md` 完成前置检测，确保 `.agents/rules/pr-sync.md` 所需的运行时上下文已就绪。
 
 失败处理与「按需更新任务状态」一致：警告但**不**阻塞已完成的 `git commit`。
 
-## 7. 完成校验
+## 8. 完成校验
 
 如果本次操作关联了 `{task-id}`，运行完成校验，确认任务元数据和同步状态符合规范；如果没有任务上下文，跳过本步骤。
 

package/templates/.agents/skills/commit/config/verify.json

@@ -17,9 +17,10 @@
       "expected_action_pattern": "Commit",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "pr_number_exists",
       "expected_pr_comment_marker": "<!-- sync-pr:{task-id}:summary -->",
+      "verify_in_labels_computed": true,
       "verify_pr_comment_last_commit_matches_head": true
     }
   }

package/templates/.agents/skills/commit/reference/issue-metadata-sync.en.md

@@ -0,0 +1,23 @@
+# Commit-Stage Issue Metadata Sync
+
+## Trigger Conditions
+
+Run this step only when all of the following are true:
+- `{task-id}` is valid
+- `task.md` frontmatter contains a valid `issue_number`
+
+If either condition is missing, skip this step.
+
+Read `.agents/rules/issue-sync.md` first so upstream repository detection and permission detection are complete before any sync work.
+
+## `in:` Label Sync
+
+Follow the `in:` label sync steps in issue-sync.md and refine the Issue `in:` labels from the committed branch diff (`git diff {base-branch}...HEAD --name-only`).
+
+## Requirement Checkbox Sync
+
+Follow the requirement-checkbox sync steps in issue-sync.md and sync checked items from task.md `## Requirements` into the Issue body.
+
+## Error Handling
+
+Treat sync failures as warnings only. Do not block an already completed `git commit`.

package/templates/.agents/skills/commit/reference/issue-metadata-sync.zh-CN.md

@@ -0,0 +1,23 @@
+# Commit 阶段 Issue 元数据同步
+
+## 触发条件
+
+仅当以下条件同时满足时执行：
+- `{task-id}` 有效
+- `task.md` frontmatter 中存在有效 `issue_number`
+
+任一条件不满足时，跳过本步骤。
+
+执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测。
+
+## `in:` label 同步
+
+按 issue-sync.md 的 `in:` label 同步步骤，基于已提交分支的改动文件（`git diff {base-branch}...HEAD --name-only`）精修 Issue 的 `in:` label。
+
+## 需求复选框同步
+
+按 issue-sync.md 的需求复选框同步步骤，将 task.md `## 需求` 中已勾选的条目同步到 Issue body。
+
+## 错误处理
+
+同步失败只记为警告，不阻塞已完成的 `git commit`。

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

@@ -87,11 +87,11 @@ Confirm the task directory was successfully moved.
 
 Check whether `task.md` includes a valid `issue_number`. If not, skip this step and output nothing.
 
-> Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
+> Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing, and complete upstream repository detection plus permission detection.
 
 If a valid `issue_number` exists:
 - First scan and backfill unpublished `task.md`, `analysis*.md`, `plan*.md`, `implementation*.md`, `review*.md`, and `refinement*.md` comments using the backfill rules in `.agents/rules/issue-sync.md` (`task.md` uses the idempotent update path)
-- Backfill checked `## Requirements` items to the Issue body
+- Backfill checked `## Requirements` items to the Issue body by following the requirements-checkbox sync steps in issue-sync.md
 - Do not set any `status:` label — status labels are automatically cleared when the Issue is closed
 - Finally create or update the summary comment marked with `<!-- sync-issue:{task-id}:summary -->`
 

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

@@ -87,11 +87,11 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过此步骤且不输出任何内容。
 
-> Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
+> Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件，完成 upstream 仓库检测和权限检测。
 
 如果存在有效的 `issue_number`：
 - 先按 `.agents/rules/issue-sync.md` 的补发规则扫描并补发未发布的 `task.md`、`analysis*.md`、`plan*.md`、`implementation*.md`、`review*.md`、`refinement*.md` 评论（`task.md` 走幂等更新路径）
-- 兜底同步 `## 需求` 中已勾选的条目到 Issue body
+- 按 issue-sync.md 的需求复选框同步步骤，兜底同步 `## 需求` 中已勾选的条目到 Issue body
 - 不要设置 `status:` label — Issue 关闭后 status label 会被自动清除
 - 最后创建或更新 `<!-- sync-issue:{task-id}:summary -->` 标记的 summary 评论
 

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

@@ -23,7 +23,7 @@
     "completion-checklist": {
       "require_all_checked": true
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:summary -->",
       "verify_task_comment_content": true,

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

@@ -21,7 +21,7 @@ Create the base GitHub Issue from `task.md` and write `issue_number` back to the
 
 Check:
 - `.agents/workspace/active/{task-id}/task.md`
-- read `.agents/rules/issue-pr-commands.md` first, then use its authentication commands to verify platform access
+- read `.agents/rules/issue-pr-commands.md` first, then follow its prerequisite steps to complete authentication and code-hosting platform detection
 
 If `issue_number` already exists and is not empty or `N/A`, confirm with the user before creating a replacement Issue.
 
@@ -41,6 +41,8 @@ Detect `.github/ISSUE_TEMPLATE` files and decide whether to use a matched templa
 
 Create and enrich the Issue by following the "Create Issue" and "Set the Issue Type" sections in `.agents/rules/issue-pr-commands.md`. Omit label arguments when nothing valid remains.
 
+Handle labels, milestone, Issue Type, and assignee behavior by following the permission-degradation rules in `.agents/rules/issue-pr-commands.md` and `.agents/rules/issue-sync.md`.
+
 ### 5. Update Task Status
 
 Get the current time:

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

@@ -21,7 +21,7 @@ description: "从任务文件创建 GitHub Issue"
 
 检查：
 - `.agents/workspace/active/{task-id}/task.md`
-- 执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的认证命令验证当前平台访问能力
+- 执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的前置步骤完成认证和代码托管平台检测
 
 如果 `issue_number` 已存在且既不为空也不为 `N/A`，创建前必须先与用户确认。
 
@@ -41,6 +41,8 @@ description: "从任务文件创建 GitHub Issue"
 
 按 `.agents/rules/issue-pr-commands.md` 中的 “创建 Issue” 与 “Issue Type 设置” 规则创建并补充 Issue；如果没有有效 label，就省略 label 参数。
 
+Label、milestone、Issue Type 和 assignee 的具体处理方式，都按 `.agents/rules/issue-pr-commands.md` 与 `.agents/rules/issue-sync.md` 中的权限降级规则执行。
+
 ### 5. 更新任务状态
 
 获取当前时间：

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

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

package/templates/.agents/skills/create-issue/reference/label-and-type.en.md

@@ -44,12 +44,17 @@ Issue Type fallback mapping:
 
 Before creating the Issue, read `.agents/rules/issue-pr-commands.md` and use its "Create an Issue" command template.
 
+Before calling the creation command, follow `.agents/rules/issue-sync.md` / `.agents/rules/issue-pr-commands.md` to complete the prerequisite authentication and code-hosting platform detection steps.
+
 If no valid labels remain, omit label arguments.
 
 For milestone inference, read `.agents/rules/milestone-inference.md` and follow "Phase 1: `create-issue`" before creating the Issue.
 
 Issue Type setup follows the matching commands in `.agents/rules/issue-pr-commands.md`.
 
+- handle direct writes for labels, milestones, `in:` labels, and Issue Type by following the permission-degradation rules in `.agents/rules/issue-pr-commands.md` and `.agents/rules/issue-sync.md`
+- when those rules say to skip a direct write, continue without failing Issue creation
+
 `in:` labels (coarse selection):
 
 Prepare label edit arguments by following the Issue update command in `.agents/rules/issue-pr-commands.md`.
@@ -61,6 +66,6 @@ Use the returned labels to do semantic matching against the task.md title and de
 
 Principle: prefer missing labels over wrong labels. Coarse selection does not need to be perfect because implement-task / create-pr will refine `in:` labels from actual changed files later.
 
-Only add relevant `in:` labels. Do not fail Issue creation when `in:` labels are unavailable or irrelevant.
+Handle relevant `in:` labels by following the permission-degradation rules in `.agents/rules/issue-sync.md`. Do not fail Issue creation when `in:` labels are unavailable, irrelevant, or skipped by those rules.
 
 Skip unavailable labels, Issue Types, or milestones without failing the Issue creation flow.

package/templates/.agents/skills/create-issue/reference/label-and-type.zh-CN.md

@@ -44,12 +44,17 @@ Issue Type fallback 映射：
 
 创建 Issue 时，执行前先读取 `.agents/rules/issue-pr-commands.md`，并使用其中的 “创建 Issue” 命令模板。
 
+调用创建命令前，先按 `.agents/rules/issue-sync.md` / `.agents/rules/issue-pr-commands.md` 完成前置步骤中的认证和代码托管平台检测。
+
 如果最终没有有效 label，就省略 label 参数。
 
 Milestone 推断规则见 `.agents/rules/milestone-inference.md` 的「阶段 1：`create-issue`」。推断前先读取该文件。
 
 Issue Type 设置同样遵循 `.agents/rules/issue-pr-commands.md` 中的对应命令。
 
+- Label、milestone、`in:` label 和 Issue Type 的直接设置，都按 `.agents/rules/issue-pr-commands.md` 与 `.agents/rules/issue-sync.md` 的权限降级规则处理
+- 当规则判定应跳过直接写入时，继续创建 Issue，不要让流程失败
+
 `in:` label（粗选）：
 
 执行前先按 `.agents/rules/issue-pr-commands.md` 的 Issue 更新命令准备 label 编辑参数。
@@ -61,6 +66,6 @@ Issue Type 设置同样遵循 `.agents/rules/issue-pr-commands.md` 中的对应
 
 原则：宁缺毋滥。粗选阶段不求精确，后续 implement-task / create-pr 阶段会基于实际改动文件精修。
 
-只添加相关的 `in:` label。当 `in:` label 不可用或不相关时，不要让创建 Issue 流程失败。
+相关 `in:` label 的添加按 `.agents/rules/issue-sync.md` 的权限降级规则处理。当 `in:` label 不可用、不相关或规则判定应跳过时，不要让创建 Issue 流程失败。
 
 当 label、Issue Type 或 milestone 不可用时，应跳过并继续，不要让 Issue 创建失败。

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

@@ -38,7 +38,7 @@ Confirm whether the current branch already has an upstream. Push with `git push
 
 Check whether the current branch already has a PR first; if one exists, show the PR URL and stop without repeating metadata sync or summary publication.
 
-Read `.agents/rules/issue-pr-commands.md` before this step, then create the PR with its "Create a PR" command template.
+Read `.agents/rules/issue-pr-commands.md` before this step, follow its prerequisite steps to complete authentication and code-hosting platform detection, then create the PR with its "Create a PR" command template.
 
 If `{task-id}` is available and the related task provides `issue_number`, keep `Closes #{issue-number}` in the PR body.
 
@@ -46,9 +46,9 @@ If `{task-id}` is available and the related task provides `issue_number`, keep `
 
 For PRs where `{task-id}` is available, sync the core metadata immediately:
 - query standard labels, Issue metadata, and PR metadata via `.agents/rules/issue-pr-commands.md`
-- add the mapped type label and relevant `in:` labels with the PR update command from `.agents/rules/issue-pr-commands.md`
-- sync the linked Issue `in:` labels to match by following the `in:` label sync rule in `.agents/rules/issue-sync.md`
-- reuse the Issue milestone by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`
+- apply the mapped type label by following the PR update commands and permission-degradation rules in `.agents/rules/issue-pr-commands.md`
+- copy the current Issue `in:` labels to the PR without recomputing them and without writing back to the Issue
+- reuse the Issue milestone by following "Phase 3: `create-pr`" and its permission rules in `.agents/rules/milestone-inference.md`
 - keep Development linking in the PR body with `Closes #{issue-number}` when applicable
 
 ### 7. Publish the Review Summary

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

@@ -38,7 +38,7 @@ description: "创建 Pull Request 到目标分支"
 
 先检查当前分支是否已经存在 PR；如果已存在，直接告知用户 PR URL 并结束，不要重复执行元数据同步或摘要发布。
 
-执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的 “创建 PR” 命令创建 PR。
+执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的前置步骤完成认证和代码托管平台检测；随后按其中的 “创建 PR” 命令创建 PR。
 
 如果获取到 `{task-id}` 且对应任务提供了 `issue_number`，必须在 PR 正文中保留 `Closes #{issue-number}`。
 
@@ -46,9 +46,9 @@ description: "创建 Pull Request 到目标分支"
 
 对获取到 `{task-id}` 的 PR，立即同步这些核心元数据：
 - 按 `.agents/rules/issue-pr-commands.md` 查询标准 label / Issue / PR 元数据
-- 按 `.agents/rules/issue-pr-commands.md` 的 PR 更新命令添加 type label 与相关 `in:` labels
-- 按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则，同步更新关联 Issue 的 `in:` label 保持一致
-- 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」复用 Issue milestone
+- 按 `.agents/rules/issue-pr-commands.md` 的 PR 更新命令和权限降级规则处理 type label
+- 将 Issue 当前的 `in:` labels 复制到 PR（不重新计算，不反向更新 Issue）
+- 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」及其权限规则复用 Issue milestone
 - 通过 `Closes #{issue-number}` 保持 Development 关联
 
 ### 7. 发布审查摘要

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

@@ -17,10 +17,12 @@
       "expected_action_pattern": "PR Created",
       "freshness_minutes": 30
     },
-    "github-sync": {
+    "platform-sync": {
       "when": "issue_number_exists",
       "expected_pr_comment_marker": "<!-- sync-pr:{task-id}:summary -->",
       "verify_in_labels_match_pr": true,
+      "verify_pr_type_label": true,
+      "verify_pr_assignee": true,
       "verify_milestone": true
     }
   }

package/templates/.agents/skills/create-pr/reference/pr-body-template.en.md

@@ -27,6 +27,8 @@ git diff <target-branch>...HEAD
 
 Read `.agents/rules/issue-pr-commands.md` before this step.
 
+Before syncing linked Issue metadata, complete authentication and code-hosting platform detection through that rule. Keep `gh pr list` / `gh pr create` on the current repository.
+
 Before syncing labels, verify the standard label system:
 
 ```bash
@@ -50,11 +52,12 @@ Type label mapping:
 
 Metadata sync order:
 1. query Issue labels and milestone via the Issue read command in `.agents/rules/issue-pr-commands.md`
-2. add the mapped type label via the PR update command in `.agents/rules/issue-pr-commands.md`
-3. inherit non-`type:` and non-`status:` Issue labels via repeated PR update commands from the same rule
-4. refine the PR `in:` labels by following `.agents/rules/issue-sync.md`, and keep the linked Issue `in:` labels in sync with the same result
-5. handle the milestone by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`, reusing the Issue milestone directly
-6. ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword
+2. build `{label-args}` from the mapped type label, non-`type:` / non-`status:` Issue labels, and the current Issue `in:` labels (commit already computed them, so do not recompute them here and do not write back to the Issue)
+3. build `{milestone-arg}` by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md` and reusing the Issue milestone directly
+4. pass `{label-args}` and `{milestone-arg}` atomically to `gh pr create` by using the create-PR command template and permission-degradation rules in `.agents/rules/issue-pr-commands.md`
+5. ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword
+
+If those rules say to skip the direct metadata arguments above, keep only the PR body linkage plus later comment sync.
 
 Milestone rule:
 - Follow "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`
@@ -63,7 +66,7 @@ Milestone rule:
 ## Create the PR
 
 - Extract `issue_number` from task.md when this work belongs to an active task
-- If `issue_number` exists, query the Issue via `.agents/rules/issue-pr-commands.md`
+- If `issue_number` exists, complete the prerequisite code-hosting platform detection steps first, then query the Issue via `.agents/rules/issue-pr-commands.md`
 - Before calling the PR creation command, check whether the current branch already has a PR. If it does, report the PR URL and state, then stop without repeating metadata sync or summary publication
 - Use HEREDOC to pass the PR body
 - Replace `{$IssueNumber}` in the template when present

package/templates/.agents/skills/create-pr/reference/pr-body-template.zh-CN.md

@@ -27,6 +27,8 @@ git diff <target-branch>...HEAD
 
 执行前先读取 `.agents/rules/issue-pr-commands.md`。
 
+同步关联 Issue 元数据前，先按该规则完成认证和代码托管平台检测；`gh pr list` / `gh pr create` 仍保持作用于当前仓库。
+
 在同步 label 之前，先确认标准 label 体系已经存在：
 
 ```bash
@@ -50,11 +52,12 @@ Type label 映射：
 
 元数据同步顺序：
 1. 按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询关联 Issue 的 labels 和 milestone
-2. 按 `.agents/rules/issue-pr-commands.md` 的 PR 更新命令添加映射后的 type label
-3. 按同一规则的 PR 更新命令继承非 `type:`、非 `status:` 的 Issue labels
-4. 按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则精修 PR 的 `in:` label，同时同步更新关联 Issue 的 `in:` label 保持一致
-5. 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」处理 milestone，直接复用 Issue milestone
-6. 确保 PR 正文包含 `Closes #{issue-number}` 或等价的 closing keyword
+2. 构建 `{label-args}`：包含映射后的 type label、非 `type:`/`status:` 的 Issue labels，以及 Issue 当前的 `in:` labels（commit 阶段已完成计算，此处不重新计算也不反向更新 Issue）
+3. 构建 `{milestone-arg}`：按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」直接复用 Issue milestone
+4. 按 `.agents/rules/issue-pr-commands.md` 的创建 PR 命令模板与权限降级规则，将 `{label-args}` 和 `{milestone-arg}` 原子化传入 `gh pr create`
+5. 确保 PR 正文包含 `Closes #{issue-number}` 或等价的 closing keyword
+
+如果上述规则判定应跳过直接元数据参数写入，则只保留 PR 正文中的关联信息与后续评论同步。
 
 Milestone 规则：
 - 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」处理
@@ -63,7 +66,7 @@ Milestone 规则：
 ## 创建 PR
 
 - 当当前工作属于活动任务时，从 task.md 中提取 `issue_number`
-- 如果存在 `issue_number`，按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询对应 Issue
+- 如果存在 `issue_number`，先完成前置步骤中的代码托管平台检测，再按 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询对应 Issue
 - 在调用 PR 创建命令前，先检查当前分支是否已经存在 PR；如果已存在，直接告知用户 PR URL 和状态并结束，不要重复同步元数据或摘要
 - 使用 HEREDOC 传递 PR 正文
 - 如果模板中存在 `{$IssueNumber}`，替换它

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

@@ -54,7 +54,7 @@ Read `.agents/rules/release-commands.md` before this step.
 - When generating release notes in Step 7, **must** follow both the historical format style and the full category list gathered in Step 3
 - If no historical release notes exist, use the default format defined in Step 7
 
-### 4. Collect Merged PRs
+### 4. Collect Merged PRs and Contributors
 
 Get the date range between tags, then query merged PRs:
 
@@ -71,6 +71,17 @@ Also collect direct commits without PRs:
 git log v<prev-version>..v<version> --format="%H %s" --no-merges
 ```
 
+Collect collaborative contributors from commit `Co-authored-by` trailers:
+
+```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
+```
+
+Each output line is `Name <email>` and `uniq -c` provides the number of commits where that identity appeared as a co-author within the range.
+
 ### 5. Collect Related Issues
 
 From each PR body, extract linked Issues:
@@ -115,7 +126,21 @@ If no historical release notes exist, use the following default Markdown format:
 1. Item format: `- [scope] Description by @author in [#N](url)`
 2. Issue + PR: `in [#Issue](url) and [#PR](url)`
 3. Description: Use PR title, remove `type(scope):` prefix, capitalize first letter
-4. Contributors: Deduplicated, sorted by contribution count (descending)
+4. **Contributor collection**:
+   - **Data sources**:
+     - PR authors from Step 4 `gh pr list --json author`
+     - Commit co-authors from Step 4 `git log ... --format='%(trailers:key=Co-authored-by,valueonly,unfold)'`
+   - **Contribution count**: `PR count + co-authored commit count` for the same identity, merged across both sources
+   - **Name -> `@login` mapping**:
+     - Raw `Co-authored-by` values are `Name <email>` and must be mapped to a GitHub `@login`
+     - Prefer email extraction: if it matches `(\d+\+)?(\S+?)@users\.noreply\.github\.com`, use the second capture group lowercased; this regex covers both `{id}+{login}@users.noreply.github.com` and `{login}@users.noreply.github.com`
+     - Otherwise use a Name heuristic: take the first token before a space and lowercase it, for example `Claude Opus 4.6 (1M context)` -> `@claude`, `Codex` -> `@codex`, `Gemini` -> `@gemini`
+     - If the login already appears in the PR author list, merge counts into that login so `Claude` and `@claude` do not become separate entries
+     - Merge all Name variants that map to the same login before counting and sorting; for example, `Claude` and `Claude Opus 4.6 (1M context)` should both collapse into `@claude`
+     - Preserve bot identities as-is, for example `dependabot[bot]`
+     - If the login still cannot be determined reliably, output `@{lowercased first Name token}` and append `<!-- TODO(reviewer): confirm GitHub login for {original Name <email>} -->` below the `Contributors` section
+   - **Sorting**: descending by contribution count, then lexicographically by login for ties
+   - **Deduplication**: use the final mapped `@login` as the key
 5. Empty sections: Omit sections with no entries
 
 ### 8. Present and Confirm