jiantw83
920c68087e
What：`tools/gitea.sh` 的 `resolve_wiki_repo()` 允許清單加入 `SKILLSET`，`wiki-repo` 的用法註解同步。`skills/wiki/SKILL.md` 第 2 步的允許頁型補上 `SKILLSET`，同時補上先前漏列的 `CHECK` 與 `REPORT`；`description` 的呼叫端清單補上「`jsc-meta` 的 `SKILLSET` 頁」。
Why：`jsc-meta` 的四支異動技能收尾要把驗證結果寫進 `SKILLSET_{HASH}`，而所有 wiki 讀寫都走這一支技能與這一支腳本。頁型不在允許清單裡，`wiki-repo` 會直接 exit 2，報告一個字也寫不進去。`CHECK` 與 `REPORT` 是另一件事：腳本早就支援，技能的允許清單卻沒補，照技能寫的走會以為那兩種頁型不合法。
How：只加類型名，解析規則不動——`JSC_WIKI_REPO_SKILLSET` 優先，未設定才退回 `JSC_WIKI_REPO`，不做跨類型代用，兩個都沒有仍是 exit 3 交回技能問使用者。雜湊來源是被改動的 domain 存取庫 `{owner}/{repo}`，用的是同一支 `hash-id`，所以這裡不必為它多寫一條特例（`CHECK` 那種主機加帳號的例外才需要）。
Who：`jsc-gitea:wiki` 技能與 `jsc-meta` 四支異動技能的異動報告寫入路徑。
3.8 KiB
3.8 KiB
name, description
| name | description |
|---|---|
| wiki | Read or write a Gitea wiki page through tools/gitea.sh and tools/hash-id. Resolve the wiki repo per page type with JSC_WIKI_REPO_{TYPE} first, then JSC_WIKI_REPO, and ask only when neither is set. Page content is chart-first - prefer mermaid diagrams and markdown tables over plain prose. Callers are jsc-ask, jsc-sdlc, jsc-log, jsc-hooks for its ERROR pages, jsc-cli for its CHECK pages, and jsc-meta for its SKILLSET pages. Use for any wiki page in the skill set; not for repo code files. |
wiki — read and write Gitea wiki pages
Every wiki operation in the jsc skill set goes through this skill. One entry point, one permission path.
Resolve the wiki location
Different page types can live in different {owner}/{repo} repos, classified by the page-name prefix.
- Before asking the user, inspect the current shell environment for the needed repo variables and Gitea connection variables:
JSC_WIKI_REPO_{TYPE},JSC_WIKI_REPO,GITEA_HOST, andGITEA_TOKEN(also checktea login listfor a usable login token whenGITEA_TOKENis unset). Use inherited shell values first; only ask when the needed repo or connection value cannot be resolved after that check. Done when every one of those variables is either resolved from the environment or listed as missing. - Run
tools/gitea.sh wiki-repo {TYPE}(TYPE = the page-name prefix). Allowed types areQUESTION,PLAN,ANALYZE,DELIVER,MAINTAIN,REPO,LOG,LEARN,ERROR,CHECK,REPORT, andSKILLSET. Resolution order isJSC_WIKI_REPO_{TYPE}first, thenJSC_WIKI_REPO. Never borrow another type's repo. Done when the command has printed exactly one{owner}/{repo}, or exited 3 and sent this page type to step 3. - On exit 3 (neither is set after env inspection), ask the user for that page type's
{owner}/{repo}per thejsc-ask:askrules, and suggest settingJSC_WIKI_REPO_{TYPE}(can differ per type) orJSC_WIKI_REPO(shared default). Done when the user has supplied one{owner}/{repo}for that page type.
Operations
| Action | Command |
|---|---|
| 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) |
| page URL | tools/gitea.sh wiki-url {owner}/{repo} {page} — the page's absolute URL, taken from the API's html_url (exit 4 when the page is missing) |
When writing a page, link same-type pages with the [[display|page]] form (display text on the LEFT) and cross-type pages with the absolute URL from wiki-url, because [[...]] resolves only inside one wiki. Full rules and the direction trap: references/wiki-links.md.
Rules
- Page names must follow the wiki naming table in the skill guidelines (see
jsc-meta/references/guidelines.md). - Use
tools/hash-idfor{HASH}values. It returns the first 8 uppercase SHA-1 hex chars, orHplus the first 7 chars when the raw hash starts with0-9,A,B, orC. - To update a contents page (
*_CONTENTS):wiki-getit first, apply the template to append or modify, thenwiki-putthe whole page back. Never overwrite entries owned by others. - Write all wiki content in UTF-8 Traditional Chinese, per the STE100 output rule.
- Prefer visual forms for page content: use mermaid diagrams (flowchart, sequence, gantt, pie) and markdown tables wherever the information allows. Prose is capped at 3 sentences per section, and a sentence stays only when neither a mermaid diagram nor a markdown table can carry the same information.
tools/gitea.shretries once with the tea CLI login token whenGITEA_TOKENis missing or the response is 401/403. Report a failure only after that retry also fails.