1

    Hooks & Settings for Claude Code

    by Markus Isaksson

    Master Claude Code's settings hierarchy and hook framework to automate workflows and silence repetitive prompts.

    Updated May 2026
    0 installs

    Free

    One-time purchase

    Included in download

    • Downloadable skill package
    • Works with the hook event names (`PreToolUse`, `PostToolUse`
    • 1 permission declared
    • Instant install

    Sample Output

    A real example of what this skill produces.

    Added to .claude/settings.json: { "permissions": { "allow": ["Bash(npm test:*)"] }, "hooks": { "PostToolUse": [{ "matcher": "Edit|Write", "hooks": [{ "type": "command", "command": "npx prettier --write "$CLAUDE_FILE_PATH" || true" }] }] } } Restart Claude Code to apply.

    About This Skill

    Optimize Your Claude Code Workflow

    Stop re-approving the same shell commands and re-explaining your preferences in every new session. This developer-centric skill masters the Claude Code three-tier settings system (user, project, and project-local) and the powerful hook framework.

    What Problem It Solves

    New users often struggle with "configuration drift"—putting project rules in personal memory or global settings in committed project files. This skill provides a structured architecture for durable agent behavior, ensuring your environment is stable, collaborative, and automated.

    High-Level Capabilities

    • Durable Configuration: Expertly distribute rules across settings, CLAUDE.md, and memory surfaces.
    • Granular Permissions: Implement narrow allow/deny patterns for Bash commands to balance safety and speed.
    • Event-Driven Hooks: Automate workflows using PreToolUse and PostToolUse events (e.g., auto-formatting after edits).
    • Collaborative Standards: Set up shared .claude/settings.json files that work for the whole team without leaking credentials.

    The Output

    The skill produces structured JSON configuration files tailored to your specific OS and project needs. It doesn't just "guess"; it follows a rigorous 5-phase operating procedure to ensure hooks are idempotent, fast, and correctly scoped.

    Use Cases

    • Auto-allow safe Bash patterns like 'npm test' to reduce manual approvals.
    • Trigger Prettier or Linters automatically after every file write.
    • Setup desktop notifications for when long-running agent tasks complete.
    • Create a project-wide configuration safe for team-wide Git commits.
    • Audit and log every Bash command executed by the agent to a local file.

    Reviews

    No reviews yet - be the first to share your experience.

    Only users who have downloaded or purchased this skill can leave a review.

    Security Scanned

    Passed automated security review

    Permissions

    Terminal / Shell

    This skill is **specifically for Claude Code**. The three-tier settings hierarchy, the hook event names (`PreToolUse`, `PostToolUse`, `UserPromptSubmit`, `Stop`), and the permissions allow/deny patterns are Claude Code's specific design. Grok Build, Cursor, Codex CLI, and Gemini CLI all have their own configuration models — different file paths, different event names, different semantics. No direct sibling skill exists for those agents.

    Frequently Asked Questions

    More Premium Skills

    Free