feat(ask): 匯入 jsc-ask 技能組並統一 marketplace 為 jsc #2

Merged
admin merged 10 commits from develop into master 2026-08-21 06:40:43 +00:00
Showing only changes of commit d2def4abb9 - Show all commits
+17 -17
View File
@@ -3,27 +3,27 @@ name: ask
description: Decision-tree questioning until no doubt remains. Check wiki QUESTION_CONTENTS and QUESTION_{HASH} first and never re-ask answered questions. Every option must state its impact scope. After each answer, save the record back to the wiki. Use whenever a jsc skill needs user input; skip recording when no {owner}/{repo} is known.
---
# ask — 決策樹問詢
# ask — decision-tree questioning
所有 jsc 技能需要問使用者時,一律依本技能的規則進行。
Every jsc skill that needs user input MUST follow the rules in this skill.
## 問前檢查
## Before asking
1. 確認目前工作的存取庫名稱 `{owner}/{repo}`;沒有就跳過第 2、3 步,直接問但**不紀錄**。
2. 計算 `HASH`:`printf '%s' "{owner}/{repo}" | sha1sum | cut -c1-8 | tr a-f A-F`。
3. 經由 `jsc-gitea:wiki` 讀取 `QUESTION_CONTENTS` 與 `QUESTION_{HASH}`;**問詢紀錄已有答案的問題不得再問**,直接採用紀錄的答案。
1. Confirm the repository name `{owner}/{repo}` of the current work. Without one, skip steps 2 and 3: ask directly but do NOT record.
2. Compute `HASH`: `printf '%s' "{owner}/{repo}" | sha1sum | cut -c1-8 | tr a-f A-F`.
3. Read `QUESTION_CONTENTS` and `QUESTION_{HASH}` via `jsc-gitea:wiki`. Never re-ask a question already answered in the record; use the recorded answer directly.
## 問詢規則
## Questioning rules
1. 問題採決策樹的**選項方式**呈現(AskUserQuestion 或等效選單),一次一個決策點。
2. 一題只含**一個概念**,不問複合題;重要的決策點先問(可能只有一次問答機會)。
3. 每個選項都必須告知**影響範圍**(選了會發生什麼、影響哪些檔案或流程);容易被誤讀的問題加一行「為什麼重要」。
4. 依上一題答案決定下一題,直到沒有疑慮;只要還有未決事項就繼續問。
5. 只問使用者才能回答的事;程式碼、設定檔、環境變數可查到的答案自己查。
1. Present questions as decision-tree options (AskUserQuestion or an equivalent menu), one decision point at a time.
2. One question carries one concept; no compound questions. Ask the most important decision first — you may only get one round of answers.
3. Every option MUST state its impact scope (what happens if chosen; which files or flows it affects). Add one "why this matters" line to any question that is easy to misread.
4. Let each answer decide the next question. Continue until no doubt remains; keep asking while anything is undecided.
5. Ask only what the user alone can answer. Look up answers available in code, config files, or environment variables yourself.
## 問後紀錄
## After asking
1. 沒有存取庫名稱就不紀錄,結束。
2. 每次問答完成,套用 `templates/question-record.md` 建立或更新 `QUESTION_{HASH}`(附加新問答,不覆蓋舊紀錄)。
3. 套用 `templates/question-contents.md` 建立或更新 `QUESTION_CONTENTS`(該存取庫的列不存在就新增,存在就更新最後更新時間)。
4. 以上 wiki 寫入**必須以 sub agent 執行**,主 agent 只確認寫入成功。
1. Without a repository name, do not record; stop here.
2. After each Q&A round, apply `templates/question-record.md` to create or update `QUESTION_{HASH}` (append new entries; never overwrite old records).
3. Apply `templates/question-contents.md` to create or update `QUESTION_CONTENTS` (add the repository row if missing; otherwise refresh its last-updated time).
4. The wiki writes above MUST run as a sub agent; the main agent only confirms the write succeeded.