From b1a6f9b36e19f926e1574d09ad75ee942dbcbca2 Mon Sep 17 00:00:00 2001 From: Jeffery Date: Fri, 21 Aug 2026 14:29:45 +0800 Subject: [PATCH] docs(gitea): translate SKILL.md into English per guidelines Co-Authored-By: Claude Fable 5 --- skills/repo-sync/SKILL.md | 20 ++++++++++---------- skills/wiki/SKILL.md | 30 +++++++++++++++--------------- 2 files changed, 25 insertions(+), 25 deletions(-) diff --git a/skills/repo-sync/SKILL.md b/skills/repo-sync/SKILL.md index b17a9dd..564d9b1 100644 --- a/skills/repo-sync/SKILL.md +++ b/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. diff --git a/skills/wiki/SKILL.md b/skills/wiki/SKILL.md index e8fbd60..8e85c5a 100644 --- a/skills/wiki/SKILL.md +++ b/skills/wiki/SKILL.md @@ -3,27 +3,27 @@ name: wiki description: Read or write a Gitea wiki page through tools/gitea.sh with GITEA_TOKEN. Resolve the wiki repo per page type (QUESTION/PLAN/ANALYZE/MAINTAIN/REPO/LOG) via gitea.sh wiki-repo, falling back to JSC_WIKI_REPO or a decision-tree question. Used by jsc-ask, jsc-sdlc, and jsc-log for all wiki pages; not for repo code files. --- -# wiki — Gitea Wiki 頁讀寫 +# wiki — read and write Gitea wiki pages -所有 jsc 技能的 wiki 操作都必須經由本技能，統一入口與權限。 +Every wiki operation in the jsc skill set goes through this skill. One entry point, one permission path. -## 決定 wiki 位置 +## Resolve the wiki location -不同類型的 wiki 頁可以放在不同的 `{owner}/{repo}`，以頁名前綴分類：`QUESTION`、`PLAN`、`ANALYZE`、`MAINTAIN`、`REPO`、`LOG`。 +Different page types can live in different `{owner}/{repo}` repos, classified by page-name prefix: `QUESTION`, `PLAN`, `ANALYZE`, `MAINTAIN`, `REPO`, `LOG`. -1. 執行 `tools/gitea.sh wiki-repo {TYPE}`（TYPE = 頁名前綴）。解析順序：`JSC_WIKI_REPO_{TYPE}` > `JSC_WIKI_REPO`；已設定就直接使用，不再詢問。 -2. exit 3（都未設定）時依 `jsc-ask:ask` 規則詢問使用者該類型頁面所在的 `{owner}/{repo}`，並建議使用者設定 `JSC_WIKI_REPO_{TYPE}`（各類型可不同）或 `JSC_WIKI_REPO`（共用預設）。 +1. Run `tools/gitea.sh wiki-repo {TYPE}` (TYPE = the page-name prefix). Resolution order: `JSC_WIKI_REPO_{TYPE}` > `JSC_WIKI_REPO`. When either is set, use it and skip the question. +2. On exit 3 (neither is set), ask the user for that page type's `{owner}/{repo}` per the `jsc-ask:ask` rules, and suggest setting `JSC_WIKI_REPO_{TYPE}` (can differ per type) or `JSC_WIKI_REPO` (shared default). -## 操作 +## Operations -| 動作 | 指令 | +| Action | Command | | --- | --- | -| 列頁 | `tools/gitea.sh wiki-list {owner}/{repo}` | -| 讀頁 | `tools/gitea.sh wiki-get {owner}/{repo} {page}`（不存在 exit 4） | -| 寫頁 | 內容先寫入暫存檔，再 `tools/gitea.sh wiki-put {owner}/{repo} {page} {file}`（自動判斷新建或更新） | +| list pages | `tools/gitea.sh wiki-list {owner}/{repo}` | +| read page | `tools/gitea.sh wiki-get {owner}/{repo} {page}` (exit 4 when missing) | +| write page | write the content to a temp file first, then `tools/gitea.sh wiki-put {owner}/{repo} {page} {file}` (creates or updates automatically) | -## 規則 +## Rules -1. 頁面命名必須符合技能準則的「Wiki 頁命名總表」（見 `jsc-meta/references/guidelines.md`）。 -2. 更新目錄頁（`*_CONTENTS`）時先 `wiki-get` 取回，套用範本附加或修改後再整頁 `wiki-put`，不可覆蓋他人條目。 -3. 內容一律 UTF-8 繁體中文。 +1. Page names must follow the wiki naming table in the skill guidelines (see `jsc-meta/references/guidelines.md`). +2. To update a contents page (`*_CONTENTS`): `wiki-get` it first, apply the template to append or modify, then `wiki-put` the whole page back. Never overwrite entries owned by others. +3. Write all wiki content in UTF-8 Traditional Chinese, per the STE100 output rule.