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

Merge pull request 'chore(ask): 合併 develop 到 master' (#5) from develop into master

Browse Source 
Reviewed-on: #5
Reviewed-by: 系統管理員 <1+admin@noreply.localhost>
This commit was merged in pull request #5.
This commit is contained in:
admin
2026-08-24 03:45:18 +00:00
parent a2c1815a4a 40f176921b
commit 99d9e59928
3 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -24,7 +24,7 @@ Marketplace 統一為 `jsc`（https://gitea.jsc.idv.tw/plugins/jsc.git），安
### `ask` ### `ask`
決策樹問詢：一題一個決策點、選項標明影響範圍、問到沒有疑慮為止。問前查 `QUESTION_CONTENTS` 與 `QUESTION_{HASH}`，其中 `{HASH}` 依共用 wiki hash 規則產生；已有答案不再問。問後套範本寫回 wiki（沒有存取庫名稱就不紀錄）。 決策樹問詢：一題一個決策點、選項標明影響範圍、問到沒有疑慮為止。問前查 `QUESTION_CONTENTS` 與 `QUESTION_{HASH}`，其中 `{HASH}` 依共用 wiki hash 規則產生；已有答案不再問；AI 取用舊答案時依意圖判斷適用性，意圖不符就重新問。問後套範本寫回 wiki，每節開頭記錄使用者意圖（沒有存取庫名稱就不紀錄）。
<!-- JSC-SKILLS:END --> <!-- JSC-SKILLS:END -->
skills/ask/SKILL.md
+2 -2
View File
@@ -11,7 +11,7 @@ Every jsc skill that needs user input MUST follow the rules in this skill.
1. Confirm the repository name `{owner}/{repo}` of the current work. Without one, skip steps 2 and 3: ask directly but do NOT record. 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` with the shared wiki hash rule: 8 characters, uppercase hex, and if the first character would be `0-9`, `A`, `B`, or `C`, replace it with `H` and keep the total length at 8. 2. Compute `HASH` with the shared wiki hash rule: 8 characters, uppercase hex, and if the first character would be `0-9`, `A`, `B`, or `C`, replace it with `H` and keep the total length at 8.
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. 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. When reusing an answer, read the section's intent to judge whether the answer fits the current situation and whether it extends to similar unrecorded decisions. If the intent differs from the current situation, ask again instead of forcing the old answer.
## Questioning rules ## Questioning rules
@@ -24,6 +24,6 @@ Every jsc skill that needs user input MUST follow the rules in this skill.
## After asking ## After asking
1. Without a repository name, do not record; stop here. 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). 2. After each Q&A round, apply `templates/question-record.md` to create or update `QUESTION_{HASH}` (append new entries; never overwrite old records). Each section MUST open with the user's original intent (why this questioning round happened), per the template; it lets a later reader judge why the user chose as they did and whether the answer still applies.
3. Apply `templates/question-contents.md` to create or update `QUESTION_CONTENTS` (add the repository row if missing; otherwise refresh its last-updated time). 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. 4. The wiki writes above MUST run as a sub agent; the main agent only confirms the write succeeded.
templates/question-record.md
+2
View File
@@ -4,6 +4,8 @@
## {yyyy-MM-dd HH:mm} {問詢主題} ## {yyyy-MM-dd HH:mm} {問詢主題}
- **意圖**: {使用者的原始需求與目的，一句話，供 AI 判斷選擇動機與答案適用性}
### Q1: {問題} ### Q1: {問題}
| 選項 | 影響範圍 | | 選項 | 影響範圍 |