feat(review): 技能與說明文件納入文件編號夾帶審查

What：skills/code-review/SKILL.md 的第 2 組 Obscurity 審查範圍納入 2.5，
Notes 補上與 jsc-hooks 的 comment-scope.sh 分工說明；README.md 的技能說明
與參考檔表格同步。

Why：規則正文放進 references 還不夠，sub agent 讀的是 SKILL.md 的審查範圍表。
範圍表沒寫，第 2 組就不會查這一項。使用者讀的是 README.md，參考檔沒列出來就找不到。

How：審查範圍表的第 2 組直接列出六類命中樣式，並指向 references/comment-scope.md
取完整清單。Notes 寫明 comment-scope.sh 負責樣式判定得了的項目，第 2 組負責
樣式判定不了的專案代號與客戶名稱，兩邊不重複回報。README.md 表格新增一列。

Who：jsc-review 的 code-review 技能與存取庫說明文件。

skills/code-review/SKILL.md

@@ -25,7 +25,7 @@ Review changed code against `references/smells.md` (from the book *Refactoring*)
    | Group | Scope |
    | --- | --- |
    | 1 Bloaters | smells.md group 1 |
-   | 2 Obscurity | smells.md group 2 |
+   | 2 Obscurity | smells.md group 2, including 2.5 document reference leak — comments carrying issue ids, wiki page ids, work package ids, commit hashes, @ mentions, or external document links; the full banned and allowed lists live in `references/comment-scope.md` |
    | 3 Couplers | smells.md group 3 |
    | 4 Dispensables & Others | smells.md group 4 |
    | 5 Comment contract | smells.md group 5 |
@@ -39,5 +39,6 @@ Review changed code against `references/smells.md` (from the book *Refactoring*)
 
 ## Notes
 
+- `jsc-hooks`' `comment-scope.sh` already matches the pattern-detectable items after every file write. Group 2 here covers what patterns cannot decide — project code names and customer names — plus the overall judgment; the two never report the same finding twice.
 - If group 5 examples are fetched from a database, they must be de-identified; never include personal data.
 - When there are no findings, report the literal 「無發現」 explicitly; never leave the report empty.