claude-hooks CLAUDE.md

DO NOT install or use the git cli with the environment_run_cmd tool. All environment tools will handle git operations for you. Changing ".git" yourself will compromise the integrity of your environment.

You MUST inform the user how to view your work using container-use log <env_id> AND container-use checkout <env_id>. Failure to do this will make your work inaccessible to others.

Commands

Building and Development

• bun run build - Compile TypeScript to JavaScript
• bun run lint - Run Biome linter
• bun run lint:fix - Run Biome linter with auto-fix
• bun run format - Format code with Biome

Testing

• bun test - Run all tests
• bun run test:unit - Run unit tests only
• bun run test:integration - Run integration tests
• bun run test:smoke - Run smoke tests
• bun run test:coverage - Run tests with coverage report

Clean Up

• bun run clean - Remove all build artifacts and test outputs
• bun run clean:test - Remove only test output directories

Architecture

This is an oclif-based CLI tool written in TypeScript that generates a hook system for Claude Code.

Key Components

1. Command Structure: Commands live in src/commands/. Currently, there's only the main init command that sets up the hook system.

2. Template System: Hook templates are stored in templates/ and copied to the user's .claude/ directory when initialized.

3. Hook Types: The system supports four hook types:

   • PreToolUse - Intercept tool usage before execution
   • PostToolUse - React to tool execution results
   • Notification - Handle Claude notifications
   • Stop - Handle session stop events

4. Generated Structure: Running the CLI creates:

   .claude/
   ├── settings.json      # Hook configuration
   └── hooks/
       ├── index.ts       # Main hook handlers (user edits this)
       ├── lib.ts         # Type definitions and utilities
       └── session.ts     # Session tracking utilities