Skip to content

a5c-ai/babysitter / library/methodologies/claudekit/skills/hook-management

hook-management

Verified

Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.

  • file-guard: Blocks sensitive file access (195+ patterns)

PostToolUse Hooks

  • typecheck-changed: Type checking on modified files
  • lint-changed: Linting on modified files
  • test-changed: Testing related to modified files
  • check-comment-replacement: Detects code replaced with comments
  • check-unused-parameters: Detects unused function parameters

UserPromptSubmit Hooks

  • codebase-map: Invisible project context injection
  • thinking-level: Reasoning enhancement (4 levels)

Stop/SubagentStop Hooks

  • create-checkpoint: Git-backed state snapshot
  • typecheck-project: Full project type checking
  • lint-project: Full project linting
  • test-project: Full test suite execution
  • self-review: Comprehensive change review

Session Isolation

All hook changes are session-scoped. Disabling a hook only affects the current session and does not persist.

Profiling

  • Red alert: execution time > 5s
  • Yellow warning: execution time > 3s
  • Green: execution time < 3s
  • Output size monitoring: flag > 10KB

Commands

  • /hook:enable [hookName] -- Enable a disabled hook
  • /hook:disable [hookName] -- Disable a hook for this session
  • /hook:status -- Show all hook states and profiling data

When to Use

  • When a hook is causing issues during a session
  • To check performance of hook executions
  • To temporarily bypass a hook for a specific operation

Processes Used By

  • claudekit-orchestrator (hook pipeline setup)
  • claudekit-safety-pipeline (hook profiling)
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall