docs(gitea): translate SKILL.md into English per guidelines

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

skills/repo-sync/SKILL.md

@@ -3,15 +3,15 @@ name: repo-sync
 description: Batch-sync all readable repos of a chosen Gitea owner into the working directory. List owners, let the user pick, then clone or update each repo; local changes become a branch, commit, push, and PR to develop or master. Use for workspace bootstrap or bulk refresh; not for a single repo.
 ---
 
-# repo-sync — 存取庫批次同步
+# repo-sync — batch-sync repositories
 
-## 步驟
+## Steps
 
-1. `tools/gitea.sh owners` 列出使用者擁有讀取權限的所有 `{owner}`。
-2. 依 `jsc-ask:ask` 規則讓使用者選擇要同步的 `{owner}`（選項需標明各 owner 的 repo 數量與影響範圍）。
-3. `tools/gitea.sh repos {owner}` 列出該 owner 底下可讀取的所有 `{repo}`。
-4. 逐一同步每個 `{repo}`，此步驟**必須以 sub agent 執行**（每個 repo 一個 sub agent）：
-   1. 不存在 → `git clone` 到工作目錄（clone URL 取自 `tools/gitea.sh clone-url`）。
-   2. 已存在 → 切換到 `develop`，沒有就切 `master`（或 `tools/gitea.sh default-branch` 的結果），再 `git pull`。
-   3. 有檔案變更 → 從 develop/master 新建分支，依 `jsc-git:commit` 認可、push，再依 `jsc-git:pr` 建立 PR 回 develop/master。
-5. 回報每個 repo 的同步結果（clone / 更新 / 建立 PR / 失敗原因）。
+1. Run `tools/gitea.sh owners` to list every `{owner}` the user can read.
+2. Ask the user which `{owner}` to sync, per the `jsc-ask:ask` rules. Every option states the owner's repo count and impact scope.
+3. Run `tools/gitea.sh repos {owner}` to list every readable `{repo}` under that owner.
+4. Sync each `{repo}` one by one. This step **MUST run as a sub agent** (one sub agent per repo):
+   1. Missing locally → `git clone` into the working directory (clone URL from `tools/gitea.sh clone-url`).
+   2. Present locally → switch to `develop`, else `master` (or the result of `tools/gitea.sh default-branch`), then `git pull`.
+   3. Local file changes → create a branch from develop or master, commit via `jsc-git:commit`, push, then open a PR back to develop or master via `jsc-git:pr`.
+5. Report the sync result for every repo: cloned, updated, PR created, or the failure reason.