void-doctor

Diagnose harness installation health and report broken, stale, or healthy findings with repair commands.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-doctor-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-doctor
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-doctor
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-doctor-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After installing or updating a coding-agent harness, it is hard to tell whether the configuration is actually wired up or only looks wired. This Skill runs the harness health checks and reports exactly what is broken, stale, or healthy, along with the command that repairs each finding. ## Core Features & Use Cases - Health check execution: Runs void-harness doctor (or npx voidharness doctor without an install) against the current project. - Structured reporting: Summarizes findings in priority order: broken items with their exact repair commands, stale artifacts, then a one-line healthy summary. - Report-only discipline: Never repairs automatically; the human runs the named repair command, preserving the chance to reject changes to their own files. - Use Case: After running npx voidharness update, a rule that should have blocked an edit did not fire. Invoke this Skill to check whether hooks, skills, and doctrine files are installed and active, and get the exact command to fix whatever is missing. ## Quick Start Ask the agent to run the void-doctor health check on this project and summarize what is broken, stale, and healthy.

Frequently Asked Questions about void-doctor

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

FAQPage Schema
How do I check if my void-harness installation is working?

Run `void-harness doctor` in the project, or `npx voidharness doctor` if the CLI is not installed. The report lists what is broken with the exact repair command for each finding, what is stale, and what is healthy.

How do I fix findings reported by the doctor health check?

Each broken finding in the report includes the exact command that repairs it. The Skill never repairs on its own; you run the named command yourself so you can reject changes to files you own.

Does void-doctor work with both Claude Code and Codex?

Yes. The harness metadata declares both claude and codex runtimes as active. The underlying `void-harness doctor` CLI checks whichever runtime files are installed in the project.

Why did a hook or rule not fire during my session?

A rule that should have blocked something but did not is a signal to run the doctor check. It verifies whether hooks, skills, and doctrine files are actually installed and active rather than only appearing to be.

Can void-doctor automatically repair my project configuration?

No. Automatic repair is deliberately excluded so a check never silently rewrites your configuration. Repair flags exist but run only when a human explicitly types them, never as a follow-up the Skill decides on.