plugins/gitea
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(wiki): wiki 頁型允許清單新增 LEARN

Browse Source 
What：gitea.sh 的 wiki-repo 允許型別清單、wiki 技能 SKILL.md 的頁型清單，以及 check-wiki-rules.sh 的驗證案例，同步收錄 LEARN 頁型。
Why：jsc-log 新增 LEARN wiki 頁型，若允許清單未收錄，wiki-repo LEARN 會以 unknown type（exit 2）被擋下，學習紀錄頁無法解析存放位置。
How：resolve_wiki_repo 的 case 白名單加入 LEARN，解析順序維持 JSC_WIKI_REPO_LEARN 優先、退回 JSC_WIKI_REPO、不跨型別代用；check-wiki-rules.sh 補上 LEARN 專屬變數優先與退回共用預設兩個案例；SKILL.md 允許頁型清單同步更新。
Who：jsc-gitea wiki 技能與其呼叫方（jsc-log 等）的 wiki 頁型解析功能。

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
jiantw83
2026-08-24 11:36:49 +08:00
co-authored by Claude Fable 5
parent 11082f648e
commit 653b619ea1
3 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/wiki/SKILL.md
+2 -2
View File
@@ -9,10 +9,10 @@ Every wiki operation in the jsc skill set goes through this skill. One entry poi
## Resolve the wiki location
Different page types can live in different `{owner}/{repo}` repos, classified by page-name prefix: `QUESTION`, `PLAN`, `ANALYZE`, `MAINTAIN`, `REPO`, `LOG`, `ERROR`.
Different page types can live in different `{owner}/{repo}` repos, classified by page-name prefix: `QUESTION`, `PLAN`, `ANALYZE`, `MAINTAIN`, `REPO`, `LOG`, `LEARN`, `ERROR`.
1. 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`, and `GITEA_TOKEN`. Use inherited shell values first; only ask when the needed repo cannot be resolved after that check.
2. Run `tools/gitea.sh wiki-repo {TYPE}` (TYPE = the page-name prefix). Allowed types are `QUESTION`, `PLAN`, `ANALYZE`, `MAINTAIN`, `REPO`, `LOG`, and `ERROR`. Resolution order is `JSC_WIKI_REPO_{TYPE}` first, then `JSC_WIKI_REPO`. Never borrow another type's repo.
2. Run `tools/gitea.sh wiki-repo {TYPE}` (TYPE = the page-name prefix). Allowed types are `QUESTION`, `PLAN`, `ANALYZE`, `MAINTAIN`, `REPO`, `LOG`, `LEARN`, and `ERROR`. Resolution order is `JSC_WIKI_REPO_{TYPE}` first, then `JSC_WIKI_REPO`. Never borrow another type's repo.
3. On exit 3 (neither is set after env inspection), 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