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

fix(wiki): 統一 QUESTION wiki 命名與 hash 規則

Browse Source
This commit is contained in:
jiantw83
2026-08-21 16:53:17 +00:00
parent 3df42eafe5
commit d922820451
7 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/ask/SKILL.md
+2 -2
View File
@@ -1,6 +1,6 @@
---
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.
description: Decision-tree questioning until no doubt remains. Check wiki QUESTION_CONTENTS and QUESTION_{HASH} first and never re-ask answered questions. Compute HASH with the shared 8-character wiki hash rule. 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 — decision-tree questioning
@@ -10,7 +10,7 @@ Every jsc skill that needs user input MUST follow the rules in this skill.
## Before asking
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`.
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.
## Questioning rules