Description
Add a Cursor hook compatibility verification step to the /release skill. Since Cursor could remove Claude Code hook support in any update, each release should verify that all 4 hook events still fire correctly.
Semi-automated Flow
The /release skill handles setup and analysis. The release manager runs the manual Cursor test.
Step 1: Skill prepares the test (automated)
- Create debug hook script at /tmp/debug-hook.sh
- Add debug hook entries alongside ai-guardian hooks in ~/.claude/settings.json for all events (UserPromptSubmit, PreToolUse, PostToolUse, SessionEnd)
- Clean any old debug log files
- Print instructions for the release manager
Step 2: Release manager runs manual test
- Upgrade Cursor to latest version
- Restart Cursor
- Open a project, type a prompt that triggers a file read
- Close the chat session
- Return to the release skill
Step 3: Skill analyzes results (automated)
- Read /tmp/cursor-hook-debug-*.json files
- Verify all 4 events fired with cursor_version field:
- beforeSubmitPrompt
- preToolUse
- postToolUse
- sessionEnd
- Report PASS/FAIL per event
- Clean up debug hooks from settings.json and delete debug files
- If any event missing: FAIL with warning that Cursor may have changed hook support
Expected Output
Acceptance Criteria
Files Involved
- Release skill (/.claude/skills/ or /release command)
- RELEASING.md — document Cursor verification step
- AGENTS.md — add to release checklist
Related
Description
Add a Cursor hook compatibility verification step to the /release skill. Since Cursor could remove Claude Code hook support in any update, each release should verify that all 4 hook events still fire correctly.
Semi-automated Flow
The /release skill handles setup and analysis. The release manager runs the manual Cursor test.
Step 1: Skill prepares the test (automated)
Step 2: Release manager runs manual test
Step 3: Skill analyzes results (automated)
Expected Output
Acceptance Criteria
Files Involved
Related