ワンクリックで
cc-hooks
Comprehensive Claude Code hooks configuration for notifications, validation, auto-formatting, safety checks, and context loading.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Comprehensive Claude Code hooks configuration for notifications, validation, auto-formatting, safety checks, and context loading.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cc:hooks |
| description | Comprehensive Claude Code hooks configuration for notifications, validation, auto-formatting, safety checks, and context loading. |
| author | @thesolutionarchitect |
| maksym.diabin@gmail.com |
Comprehensive Claude Code hooks configuration for notifications, validation, auto-formatting, safety checks, and context loading.
# Run setup to configure all hooks
bash .claude/skills/hooks/scripts/setup-hooks.sh
# Or invoke via skill
/hooks
After setup, restart Claude Code for hooks to take effect.
Get native desktop notifications when Claude needs your attention:
Run tests and validation before Claude stops:
npm test (configurable)npm run validate:all (configurable)Automatically format files after Claude edits them:
Block dangerous operations before they execute:
rm -rf /, dd, mkfs, fork bombs, etc..env, *.key, *.pem, secrets.json, etc.Load development context at session start:
$AGENT_DOCS_DIR/active-story.yamlEdit .claude/skills/hooks/config.yaml to customize behavior:
# Enable/disable features
notification:
enabled: true
stop_hooks:
enabled: true
run_tests: true
fail_on_test_error: false
post_tool_use:
enabled: true
formatters:
prettier:
enabled: true
black:
enabled: true
pre_tool_use:
enabled: true
safety_checks:
bash_safety:
enabled: true
session_start:
enabled: true
After changing config, re-run setup:
bash .claude/skills/hooks/scripts/setup-hooks.sh
Already installed:
Will be installed by setup:
Run setup script:
bash .claude/skills/hooks/scripts/setup-hooks.sh
Restart Claude Code:
# Exit current session and restart
claude code
Verify installation:
rm -rf / → should blockosascriptnotify-send (install via sudo apt-get install libnotify-bin)This skill preserves your existing .claude/hooks/validate-changes.sh hook. Both hooks will run in parallel:
No conflicts expected - hooks are merged automatically.
.claude/settings.json has hooks configuredchmod +x .claude/skills/hooks/hooks/*/*.shclaude --debugnpm install --save-dev prettierpip3 install blackbash .claude/skills/hooks/scripts/setup-hooks.shnotify-send: sudo apt-get install libnotify-binchmod +x .claude/skills/hooks/**/*.sh.claude/skills/hooks/config.yaml to disable specific checksblocked_patterns to be less strictAdd custom patterns to config.yaml:
pre_tool_use:
safety_checks:
bash_safety:
blocked_patterns:
- "my-dangerous-command"
Add custom formatter to post_tool_use/format-files.sh:
case "$extension" in
myext)
my-formatter "$file_path"
;;
esac
Edit config.yaml:
notification:
enabled: false # Disable notifications
Re-run setup to apply.
.claude/skills/hooks/references/hook-types.md.claude/skills/hooks/references/formatter-config.md.claude/skills/hooks/references/safety-rules.md.claude/skills/hooks/references/troubleshooting.mdTo remove all hooks:
# Clear hooks section from settings.json
# Or manually remove:
# - .claude/skills/hooks/
# - Hooks section from .claude/settings.json
Then restart Claude Code.
MIT
Injects project context (AGENT_DOCS_DIR, active story) before every skill invocation via PreToolUse hook.
Discover skills in this marketplace that match your workflow. Accepts a workload or task description, scans all released skills, and recommends the best matches with install commands. Use when users ask 'what skills are available', 'find a skill for X', 'which skill helps me with Y', 'what can I install', or 'recommend skills for my workflow'.
Collect non-functional requirements through interactive Q&A. Asks targeted questions about performance, scalability, security, reliability, and cost constraints. Invokable with /gather-nfr.
Validates business requirements compliance - generates OpenAPI specs, creates contract tests, and ensures acceptance criteria alignment
Hypothesis-driven bug investigation with mandatory regression tests
Create git commits with configurable numbering (issue-based or sequential). Analyzes staged changes and generates commit messages following project conventions. Optionally creates GitHub issues if no active story exists.