@fitlab-ai/agent-infra 0.5.2 → 0.5.4

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

@@ -8,7 +8,7 @@ description: "Mark a task as completed and archive it"
 ## 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
+- Do not move a task that has incomplete workflow steps unless forced
 
 ## Steps
 
@@ -36,7 +36,7 @@ Before marking complete, verify ALL of these:
 > - If any condition is missing -> **stop by default** and output the prerequisite warning
 > - Only continue with unmet prerequisites when the user explicitly requested `--force`
 >
-> **Do not continue to Steps 3-7 when prerequisites are not met, and do not output "Task {task-id} completed and archived."**
+> **Do not continue to Steps 3-7 when prerequisites are not met, and do not output "Task {task-id} completed; task directory moved to completed/."**
 
 If any prerequisite is not met, warn the user:
 ```
@@ -53,7 +53,7 @@ If prerequisites are not met and the user did not explicitly provide `--force`,
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -64,10 +64,10 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - Verify and check off all items in `## Completion Checklist` (change `- [ ]` to `- [x]`)
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Completed** by {agent} — Task moved to completed/
   ```
 
-### 4. Archive Task
+### 4. Move Task
 
 Move the task directory from active to completed:
 
@@ -75,7 +75,7 @@ Move the task directory from active to completed:
 mv .agents/workspace/active/{task-id} .agents/workspace/completed/{task-id}
 ```
 
-### 5. Verify Archive
+### 5. Verify Move
 
 ```bash
 ls .agents/workspace/completed/{task-id}/task.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 -->`
 
@@ -116,12 +116,12 @@ Keep the gate output in your reply as fresh evidence. Do not claim completion wi
 
 Output format:
 ```
-Task {task-id} completed and archived.
+Task {task-id} completed; task directory moved to completed/.
 
 Task info:
 - Title: {title}
 - Completed at: {timestamp}
-- Archived to: .agents/workspace/completed/{task-id}/
+- Target path: .agents/workspace/completed/{task-id}/
 
 Deliverables:
 - {List of key outputs: files modified, tests added, etc.}
@@ -132,18 +132,18 @@ Deliverables:
 - [ ] Verified all workflow steps are complete
 - [ ] Updated task.md with completed status and timestamp
 - [ ] Moved task directory to `.agents/workspace/completed/`
-- [ ] Verified archive succeeded
+- [ ] Verified move succeeded
 - [ ] Informed user of completion
 
 ## Notes
 
-1. **Premature completion**: Do not archive a task that has incomplete steps. Examples of incomplete situations:
+1. **Premature completion**: Do not move 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:
+2. **Rollback**: If a task was incorrectly moved:
    ```bash
    mv .agents/workspace/completed/{task-id} .agents/workspace/active/{task-id}
    ```

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

@@ -8,7 +8,7 @@ description: "标记任务完成并归档"
 ## 行为边界 / 关键规则
 
 - 本命令更新任务元数据并物理移动任务目录
-- 除非强制执行，不要归档有未完成工作流步骤的任务
+- 除非强制执行，不要转移有未完成工作流步骤的任务
 
 ## 执行步骤
 
@@ -36,7 +36,7 @@ description: "标记任务完成并归档"
 > - 如果任意一个条件不满足 → **默认停止**，输出前置条件未满足的警告
 > - 只有用户明确要求 `--force` 时，才可以在前置条件未满足时继续
 >
-> **禁止在前置条件未满足时继续执行步骤 3-7，也不要输出「任务 {task-id} 已完成并归档。」**
+> **禁止在前置条件未满足时继续执行步骤 3-7，也不要输出「任务 {task-id} 已完成，任务目录已转移到 completed/。」**
 
 如果任何前置条件未满足，警告用户：
 ```
@@ -53,7 +53,7 @@ Please complete the missing steps first, or use --force to override.
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -64,10 +64,10 @@ date "+%Y-%m-%d %H:%M:%S"
 - 逐项验证并勾选 `## 完成检查清单` 中的所有条目（将 `- [ ]` 改为 `- [x]`）
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Completed** by {agent} — Task moved to completed/
   ```
 
-### 4. 归档任务
+### 4. 转移任务
 
 将任务目录从 active 移动到 completed：
 
@@ -75,7 +75,7 @@ date "+%Y-%m-%d %H:%M:%S"
 mv .agents/workspace/active/{task-id} .agents/workspace/completed/{task-id}
 ```
 
-### 5. 验证归档
+### 5. 验证转移
 
 ```bash
 ls .agents/workspace/completed/{task-id}/task.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 评论
 
@@ -116,12 +116,12 @@ node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/c
 
 输出格式：
 ```
-任务 {task-id} 已完成并归档。
+任务 {task-id} 已完成，任务目录已转移到 completed/。
 
 任务信息：
 - 标题：{title}
 - 完成时间：{timestamp}
-- 归档路径：.agents/workspace/completed/{task-id}/
+- 目标路径：.agents/workspace/completed/{task-id}/
 
 交付物：
 - {关键产出列表：修改的文件、添加的测试等}
@@ -132,18 +132,18 @@ node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/c
 - [ ] 验证了所有工作流步骤已完成
 - [ ] 更新了 task.md 的完成状态和时间戳
 - [ ] 将任务目录移动到 `.agents/workspace/completed/`
-- [ ] 验证了归档成功
+- [ ] 验证了转移成功
 - [ ] 告知了用户完成情况
 
 ## 注意事项
 
-1. **过早完成**：不要归档有未完成步骤的任务。未完成的情况示例：
+1. **过早完成**：不要转移有未完成步骤的任务。未完成的情况示例：
    - 代码已编写但未提交
    - 代码已提交但未审查
    - 审查发现阻塞项但未修复
    - PR 已创建但未合并
 
-2. **回滚**：如果任务被错误归档：
+2. **回滚**：如果任务被错误转移：
    ```bash
    mv .agents/workspace/completed/{task-id} .agents/workspace/active/{task-id}
    ```

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,12 +41,14 @@ 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:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Write back `issue_number`, update `updated_at`, and append the Create Issue Activity Log entry.

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,12 +41,14 @@ 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. 更新任务状态
 
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 回写 `issue_number`，更新 `updated_at`，并追加 Create Issue 的 Activity Log。

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
@@ -69,7 +69,7 @@ Aggregate a reviewer-facing summary from those artifacts and maintain a single i
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 If `{task-id}` is available, update task.md with `pr_number`, `updated_at`, and append the PR Created Activity Log entry including metadata-sync and summary results.

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. 发布审查摘要
@@ -69,7 +69,7 @@ description: "创建 Pull Request 到目标分支"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 如果获取到了 `{task-id}`，更新 task.md 的 `pr_number`、`updated_at`，并追加 PR Created 的 Activity Log，记录元数据同步和摘要发布结果。

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

@@ -17,7 +17,7 @@
       "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,

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 edit` on the current repository.
+
 Before syncing labels, verify the standard label system:
 
 ```bash
@@ -50,12 +52,14 @@ 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
+2. handle the mapped type label via the PR update command and permission-degradation rules in `.agents/rules/issue-pr-commands.md`
+3. handle inheritance of non-`type:` and non-`status:` Issue labels via repeated PR update commands and the same permission-degradation rules
+4. copy the current Issue `in:` labels to the PR (commit already computed them, so do not recompute them here and do not write back to the Issue)
+5. handle the milestone by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`, including its permission rules, and reuse the Issue milestone directly
 6. ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword
 
+If those rules say to skip the direct metadata writes above, keep only the PR body linkage plus later comment sync.
+
 Milestone rule:
 - Follow "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md`
 - Reuse the linked Issue milestone directly instead of inferring a new PR milestone
@@ -63,7 +67,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 edit` 仍保持作用于当前仓库。
+
 在同步 label 之前，先确认标准 label 体系已经存在：
 
 ```bash
@@ -50,12 +52,14 @@ 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
+2. 按 `.agents/rules/issue-pr-commands.md` 的 PR 更新命令和权限降级规则处理映射后的 type label
+3. 按同一规则的 PR 更新命令和权限降级规则处理非 `type:`、非 `status:` 的 Issue labels 继承
+4. 将 Issue 当前的 `in:` labels 复制到 PR（commit 阶段已完成计算，此处不重新计算也不反向更新 Issue）
+5. 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」及其权限规则处理 milestone，直接复用 Issue milestone
 6. 确保 PR 正文包含 `Closes #{issue-number}` 或等价的 closing keyword
 
+如果上述规则判定应跳过直接元数据写入，则只保留 PR 正文中的关联信息与后续评论同步。
+
 Milestone 规则：
 - 按 `.agents/rules/milestone-inference.md` 的「阶段 3：`create-pr`」处理
 - PR 直接复用 Issue milestone，不再独立推断
@@ -63,7 +67,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-task/SKILL.en.md

@@ -71,8 +71,8 @@ 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}
-updated_at: {yyyy-MM-dd HH:mm:ss}
+created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
+updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 created_by: human
 current_step: requirement-analysis
 assigned_to: {current AI agent}
@@ -85,7 +85,7 @@ Note: `created_by` is `human` because the task comes from the user's description
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -95,7 +95,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `## 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
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Task Created** by {agent} — Task created from description
   ```
 
 ### 4. Verification Gate

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

@@ -71,8 +71,8 @@ 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}
-updated_at: {yyyy-MM-dd HH:mm:ss}
+created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
+updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 created_by: human
 current_step: requirement-analysis
 assigned_to: {当前 AI 代理}
@@ -85,7 +85,7 @@ assigned_to: {当前 AI 代理}
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -95,7 +95,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
-  - {yyyy-MM-dd HH:mm:ss} — **Task Created** by {agent} — Task created from description
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Task Created** by {agent} — Task created from description
   ```
 
 ### 4. 完成校验

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
 
@@ -81,7 +81,7 @@ Create `.agents/workspace/active/{task-id}/{implementation-artifact}`.
 Get the current time:
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update `.agents/workspace/active/{task-id}/task.md`:
@@ -91,11 +91,11 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - review the `## Requirements` section and only change items from `- [ ]` to `- [x]` when they are clearly satisfied by this round's implemented code and passing tests
 - record `{implementation-artifact}` for Round `{implementation-round}`
 - append:
-  `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
+  `- {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. 确定输入方案与实现轮次
 
@@ -81,7 +81,7 @@ description: "根据技术方案实施任务并输出报告"
 获取当前时间：
 
 ```bash
-date "+%Y-%m-%d %H:%M:%S"
+date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
@@ -91,11 +91,11 @@ date "+%Y-%m-%d %H:%M:%S"
 - 审查 `## 需求` 段落，仅把本轮已由代码实现且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
 - 记录 Round `{implementation-round}` 的 `{implementation-artifact}`
 - 追加：
-  `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
+  `- {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
     }