workspace-doctor

Diagnose DocMason workspace readiness and generate a blocker-first remediation plan.

135|36|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/JetXu-LLM/DocMason --skill workspace-doctor-jetxu-llm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-doctor
Source: https://github.com/JetXu-LLM/DocMason/tree/main/skills/canonical/workspace-doctor
Command: npx skills add https://github.com/JetXu-LLM/DocMason --skill workspace-doctor-jetxu-llm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses DocMason workspace readiness and surfaces blockers with actionable remediation without mutating the repo.

Core Features & Use Cases

  • Inspects local workspace state and prerequisites
  • Generates a prioritized remediation plan (blockers first, then degraded conditions)
  • Guides next steps to bootstrap, prepare, or recover the workspace safely

Quick Start

Run the workspace-doctor to diagnose the current environment and return a blocker-first remediation plan.

Frequently Asked Questions about workspace-doctor

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

FAQPage Schema
How do I diagnose DocMason workspace readiness on macOS or Linux?

The workspace diagnosis inspects local repository state, validates dependencies, and executes environment preflight checks across macOS and Linux without mutating the repository to identify configuration blockers.

What is the best way to identify environment blockers before running the DocMason runtime?

The best way to identify blockers is a diagnostic scan that checks local workspace prerequisites and summarizes structured diagnostics, prioritizing blockers first to guide safe recovery steps.

Does the workspace diagnostic require shell execution and local file access?

Yes, the workspace diagnostic requires local file access and shell execution to validate dependencies and inspect the local repository environment without mutating the codebase.

How do I generate a remediation plan for failed dependency checks in my local repo?

To generate a remediation plan, run a diagnostic that surfaces degraded conditions and blockers, returning a prioritized, actionable next-step guide to prepare or recover the workspace safely.

Can I use workspace diagnosis to validate prerequisites without modifying my repository?

Yes, you can use workspace diagnosis to validate prerequisites without modifying your repository, as the diagnostic process explicitly avoids mutating the workspace while proposing actionable next steps.