skills.rest
Heyvhuang
HeyvhuangCOMMUNITY
Explore all skills by this author →
GitHub

tool-hooks-doctor

Diagnose Claude Code hook installation and enablement statuses for skill-evolution workflows.

339|58|Updated Jan 10, 2026
Search Tags:#Claude Code#settings.json#pre-tool#post-tool#skill-evolution#hook-diagnostics#runs/evolution
One-click install
npx skills add https://github.com/Heyvhuang/ship-faster --skill tool-hooks-doctor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-hooks-doctor
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/tool-hooks-doctor
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill tool-hooks-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill quickly verifies that Claude Code evolution hooks for skill-evolution are installed and enabled, and provides a ready-to-run fix. It helps ensure runs/evolution artifacts are produced and not lost due to misconfigurations.

Core Features & Use Cases

  • Health checks for hook installation: confirms presence of pre-tool.sh, post-bash.sh, post-tool.sh, and session-end.sh in the expected directory.
  • Configuration validation: checks both project-level and global settings.json for enabled hooks and correct mappings.
  • Guided remediation: provides explicit steps or commands to fix missing or disabled hooks and to restore the evolution loop.

Quick Start

To diagnose your environment, run the checks:

  • ls -la ~/.claude/skills/skill-evolution/hooks/ 2>/dev/null || true
  • grep -n "skill-evolution/hooks/pre-tool.sh" .claude/settings.json ~/.claude/settings.json 2>/dev/null || true
  • ls -la runs/evolution 2>/dev/null || true

Frequently Asked Questions about tool-hooks-doctor

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

FAQPage Schema
How do I check if Claude Code hooks are installed and enabled correctly?▼

Validate hook installations by confirming pre-tool.sh, post-bash.sh, post-tool.sh, and session-end.sh exist in the expected directory and checking their enabled mappings in .claude/settings.json.

Why are my Claude Code evolution artifacts not being generated in the runs directory?▼

Missing runs/evolution artifacts usually indicate disabled or misconfigured hooks. Run hook diagnostics to verify settings.json entries and confirm that post-tool.sh and session-end.sh are active.

What is the best way to diagnose missing pre-tool and post-tool hook scripts in Claude Code?▼

Diagnose missing hook scripts by running a health check that examines project roots and global settings, yielding OK, PARTIAL, or MISSING status results along with explicit remediation steps.

Does the Claude Code hook diagnostic tool require any external dependencies?▼

No external dependencies are required; the hook diagnostic tool relies solely on standard shell utilities and path checks to validate hook scripts and settings.json configurations.

How do I fix a partial Claude Code hook setup for the skill-evolution workflow?▼

Fix a partial hook setup by following guided remediation steps to restore the evolution loop, adding missing hook scripts to the expected directory and enabling their mappings in settings.json.

Related Skills

Explore More Software Engineering Skills→
mshaheerzmshaheerz
1

tool-hooks-doctor

Diagnose Claude Code evolution hook installation and enablement status.

Community
Basic
paialexpaialex
1

git-guardrails-claude-code

Block dangerous git commands via a PreToolUse hook in Claude Code settings.

Community
Intermediate
Geralt1983Geralt1983
1

Hooks Automation

Automate development workflows with pre/post operation hooks and Git integration.

Community
Advanced
foundry-worksfoundry-works
4

foundry-setup

Automate initial Foundry plugin configuration for Claude Code.

Official
Advanced