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

fix(ask): 修正 skill-check 不合規項並升版至 0.0.3

Browse Source 
What：修剪 SKILL.md 的 frontmatter description 至 5 句內並補上明確的排除
觸發語句；將 SKILL.md 與兩份範本中重述的 wiki hash 演算法說明，改為指向
canonical 的 `jsc-gitea/tools/hash-id` 工具；同步更新 README.md 的 Skills
目錄描述；三份 manifest 版本號自 0.0.2 升至 0.0.3。

Why：jsc-meta:skill-check 稽核發現 SKILL.md 的 description 超過 5 句且缺少
明確排除觸發語句，且 SKILL.md 與 question-contents.md、question-record.md
重複描述同一套 wiki hash 演算法，違反「委派 canonical 工具、不重複邏輯」
的準則。

How：改寫 skills/ask/SKILL.md 的 description 為精簡版並加入排除語句；三處
重述 hash 演算法的段落，統一改寫為呼叫 `jsc-gitea/tools/hash-id`（演算法
細節見 guidelines.md）；README.md 的 ask 技能描述同步調整；plugin.json、
.claude-plugin/plugin.json、.codex-plugin/plugin.json 版本號 0.0.2 → 0.0.3。

Who：ask 技能本身（skills/ask/SKILL.md 與其範本、manifest）。
This commit is contained in:
jiantw83
2026-08-24 14:46:37 +08:00
parent ea1a2c805b
commit f40b374342
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. 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.
description: Decision-tree questioning until no doubt remains. Checks wiki QUESTION_CONTENTS and QUESTION_{HASH} first and never re-asks answered questions. Every option states 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; not for skills whose answer is already on record.
---
# 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` 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` by running `jsc-gitea/tools/hash-id {owner}/{repo}` (the shared wiki hash rule — see guidelines.md for the algorithm).
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