doctor

Validate be-harness profile, commands, Git state, and convention settings.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill doctor-kangmomin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/kangmomin/harness-plugins/tree/main/be-harness/skills/doctor
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill doctor-kangmomin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

be-harness Doctor diagnoses whether the be-harness skill can operate correctly by validating the profile, command availability, Git state, and convention settings.

Core Features & Use Cases

  • Validates profile fields and parses its content to ensure proper operation.
  • Checks command executability (build/test/lint/type-check) and local overrides compliance.
  • Verifies repository state (git initialization, mainBranch existence, and override rules) to ensure safe execution in CI or local workflows.

Quick Start

Run the doctor skill on your be-harness project to perform a comprehensive health check.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I diagnose be-harness readiness and health in my project environment?

Diagnose be-harness readiness by validating the profile, checking command availability, verifying Git state, and confirming convention settings to ensure safe execution in CI or local workflows.

What does profile validation check for in a be-harness project?

Profile validation verifies required fields and parses profile content to ensure proper operation, checking that all necessary configuration fields are present and correctly structured for the be-harness skill to function.

Can I use be-harness doctor to verify Git workflow readiness before running CI pipelines?

Yes, be-harness doctor verifies Git workflow readiness by checking Git initialization status, mainBranch existence, and local override rules to ensure safe execution in CI or local workflows.

How do I check if build, test, lint, and type-check commands are executable in my project?

Run the doctor skill to check command executability by validating whether build, test, lint, and type-check commands can be successfully executed within your be-harness project environment.

Why does be-harness require local override presence and documentation conformance checks?

Local override presence and documentation conformance checks ensure that the be-harness skill operates correctly across project environments by validating that local overrides comply with established convention settings.

What's the best way to perform a comprehensive health check on a be-harness project?

Run the doctor skill on your be-harness project to perform a comprehensive health check that validates profile fields, command executability, repository state, and convention settings in one pass.