claude-hooks

Generate CLAUDE.md updates and Git cleanup suggestions via Claude code hooks.

Updated Aug 27, 2026

Search Tags:#automation #monitoring #scripting #stop #hook #posttooluse #claude-hooks

Ready to run

npx skills add https://github.com/kimny1143/mued_v2 --skill claude-hooks-kimny1143

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-hooks
Source: https://github.com/kimny1143/mued_v2/tree/main/.claude/skills/hooks
Command: npx skills add https://github.com/kimny1143/mued_v2 --skill claude-hooks-kimny1143

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Hooks enable post-commit automation and governance of Claude-related workflows, including generating Claude prompts and Git hygiene suggestions.

Core Features & Use Cases

CLAUDE.md育成 Hook: Detects changes to scripts/mcp, db/migrations, apps/ components/ lib/ directories and updates CLAUDE.md accordingly.
Git整理 Hook: Provides stop-time Git cleanup recommendations via stderr.
Usage & creation: How to add hooks under .claude/hooks and configure triggers in settings.local.json.

Quick Start

Create a new hook script in .claude/hooks, configure triggers in settings.local.json, and observe automated proposals after commits.

Frequently Asked Questions about claude-hooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Claude workflow updates after Git commits?▼

Claude Hooks automate post-commit workflows by detecting changes to scripts, migrations, and app directories, then generating CLAUDE.md updates and Git cleanup suggestions via stderr. Configure hooks in .claude/hooks and set triggers in settings.local.json to enable automated proposals after each commit.

What file patterns and directories does Claude Hooks monitor?▼

Claude Hooks detects changes in scripts/mcp, db/migrations, apps/, app/, components/, lib/ directories and .claude/hooks shell scripts. It applies pattern-based detection to trigger CLAUDE.md updates and sends non-blocking proposals to stderr for human review.

How do I set up and configure Claude Hooks for my project?▼

Create hook scripts in .claude/hooks, define PostToolUse and Stop triggers in settings.local.json, and Claude Hooks will generate automated suggestions after commits and at session end. All proposals are sent to stderr as non-executing recommendations for manual approval.

Can Claude Hooks integrate with existing Git workflows without blocking commits?▼

Yes, Claude Hooks provides non-blocking, human-in-the-loop suggestions via stderr. Hooks execute as post-commit triggers and session-end handlers, delivering Git cleanup and CLAUDE.md proposals without interrupting your development workflow.

What's the difference between PostToolUse and Stop triggers in Claude Hooks?▼

PostToolUse triggers fire after git commit operations to detect file changes and update CLAUDE.md. Stop triggers execute at conversation end to provide Git hygiene recommendations. Both send proposals to stderr for optional implementation.

Do I need external dependencies to run Claude Hooks?▼

Claude Hooks has no external dependencies. It operates as local shell scripts under .claude/hooks with configuration via settings.local.json, enabling self-contained automation for development workflows without additional tooling.