When should I run the Doctor skill?

You should run it whenever you encounter hook errors in your chat session, after failed skill activations, or when setting up dev-system on a new machine.

What happens if the Doctor finds a critical error?

The tool will provide a specific exit code and a detailed report explaining the manual intervention required if it cannot be auto-fixed.

Can the Doctor skill automatically fix my errors?

Yes, by using the --fix flag, the skill can automatically repair common issues like non-executable hooks, UTF-8 BOM bytes, and Windows line endings (CRLF).

What does the /doctor command do?

It runs a full suite of diagnostic tests on your dev-system environment to identify issues with hooks, paths, settings files, and system dependencies.

Does it require any external dependencies?

The skill requires Bash version 4.0 or higher, the jq utility, and the standard timeout command to perform its checks successfully.

Dev-System Doctor

Name: Dev-System Doctor
Author: turbobeest

byturbobeest

•

Analytics & Monitoring

Diagnoses and repairs configuration errors, hook failures, and environment inconsistencies within the dev-system ecosystem.

About

The Dev-System Doctor skill serves as a comprehensive health check and troubleshooting utility designed to ensure your Claude Code development environment is running optimally. It automatically inspects Bash versions, JSON settings validity, hook execution permissions, and path alignments, providing actionable reports and one-click 'auto-fix' capabilities for common issues like Windows line endings or missing executable permissions. This skill is essential for maintaining a stable vibe-coding environment and recovering from failed tool activations or hook errors during high-intensity development sessions.

Key Features

3 GitHub stars
Auto-repair functionality for file permissions, line endings, and UTF-8 BOM issues
Automated environment verification for Bash, jq, and system dependencies
Validation of local and global settings files to prevent configuration conflicts
Deep inspection of hook scripts for syntax errors and execution timeouts
Support for JSON output to enable programmatic health monitoring

Use Cases

Troubleshooting hook errors or failed tool activations during a session
Cleaning up cross-platform path issues or line-ending conflicts in shared repositories
Verifying environment compatibility during initial project setup

About

Key Features

3 GitHub stars
Auto-repair functionality for file permissions, line endings, and UTF-8 BOM issues
Automated environment verification for Bash, jq, and system dependencies
Validation of local and global settings files to prevent configuration conflicts
Deep inspection of hook scripts for syntax errors and execution timeouts
Support for JSON output to enable programmatic health monitoring

Use Cases

Troubleshooting hook errors or failed tool activations during a session
Cleaning up cross-platform path issues or line-ending conflicts in shared repositories
Verifying environment compatibility during initial project setup