Why v2.2.2 still has the "Hooks use a matcher + hooks array" error

[Onetaway]

I have update to the v2.2.2

after run code-review-graph install command，the generate /.claude/settings.json is still

"hooks": {
"PostToolUse": [
{
"matcher": "Edit|Write|Bash",
"command": "code-review-graph update --skip-flows",
"timeout": 5000
}
],
"SessionStart": [
{
"command": "code-review-graph status",
"timeout": 3000
}
],
"PreCommit": [
{
"command": "code-review-graph detect-changes --brief",
"timeout": 10000
}
]
}

after that, run claude, still has this error

hooks
├ PostToolUse
│ └ 0
│ └ hooks: Expected array, but received undefined
├ PreCommit: Invalid key in record
└ SessionStart
└ 0
└ hooks: Expected array, but received undefined

[akhilv77]

I am getting the same issue. when i do claude command.

[summy00]

Claude帮我修复了:
原来 code-review-graph install 生成的 hooks 格式不对，Claude Code 要求每个事件下的条目包含 matcher 和 hooks 数组（每个 hook 有
type、command、timeout），而不是直接把 command 放在顶层。

修改内容：

• PostToolUse / SessionStart 的 hook 结构改为 { matcher, hooks: [{ type: "command", command, timeout }] } 格式
• 移除了 PreCommit（不是 Claude Code 支持的 hook 事件）

 Added 1 line, removed 1 line
       6          "hooks": [
       7            {
       8              "type": "command",
       9 -            "command": "code-review-graph update --quiet --skip-flows",
       9 +            "command": "code-review-graph update --skip-flows",
      10              "timeout": 5000
      11            }
      12          ]
  ⎿  PostToolUse:Edit hook returned blocking error  

[tirth8205]

Confirmed: v2.2.2 still has this bug. The skills.py:generate_hooks_config() function has not been updated to use the correct Claude Code hook schema. This is the same issue as #97, #163, #188, #191, #201.

PR #203 provides a complete fix but was closed without merging. The core problem in the current code is:

1. Missing nested hooks: [{type: command, command: ...}] array in each hook entry
2. PreCommit is not a valid Claude Code hook event
3. SessionStart is not a valid Claude Code hook event

This needs to be fixed in the next release.