armadillo-doctor

Runs health checks on plugin-mode projects — settings integrity, orphan detection, managed rules sync

Model	Source	Category
sonnet	core	Meta

Overview

After migrating to plugin mode (verify migration succeeded)
When plugin-mode project behaves unexpectedly
Periodic health check on plugin-mode installations
When user says “doctor”, “health check”, “diagnose plugins”

Full Reference

armadillo-doctor

Health check for plugin-mode projects. Validates settings, detects orphaned armadillo files, and audits managed vs project-local rules.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 🛡 armadillo-doctor ━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of what you're checking]  ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

When to Use

After migrating to plugin mode (verify migration succeeded)
When plugin-mode project behaves unexpectedly
Periodic health check on plugin-mode installations
When user says “doctor”, “health check”, “diagnose plugins”

Checks

Check	What It Verifies	Pass	Fail
Settings integrity	`settings.json` has `extraKnownMarketplaces` + `enabledPlugins`	Both present	Missing fields
Orphan detection	No stale armadillo-managed files remain	Clean	Managed skills/hooks/lib found
Rules sync	Counts managed vs project-local rules	Counted	— (always passes)

How It Works

Import checks from scripts/lib/doctor-plugin.js
Get managed skills list from armadillo.json manifest
Run runDoctorChecks(projectDir, { managedSkills })
Display results table with pass/fail/warn status

Output Format

┌─ Doctor Results ──────────────────────────────────┐
│ settings     ✓  marketplace + 3 plugins enabled   │
│ orphans      ✓  no stale armadillo files           │
│ rules        ✓  12 managed, 2 project-local        │
└───────────────────────────────────────────────────┘

Integration

Skill	Relationship
`armadillo-sync`	Runs doctor after migration to plugin mode
`doctor-plugin.js`	Library module with check implementations
`detect-entry-state.js`	Determines if project is in plugin mode