AgentHub/plugins/agenthub/commands/agenthub-doctor.md at 2b8f83d2dd04bb35fd44e6efbe6da5760ab81e67

Files

T

nntrivi2001 2b8f83d2dd refactor(lanes): drop the workflow skills and Superpowers link; pipelines go dormant

The plugin stops shipping its workflow layer:
- skills/ship-feature and skills/ship-feature-lane, the 18 stage/ship slash
  commands (plugin.json keeps agenthub-doctor/update/open), and all four
  agents/ (qc-local, senior-gate-reviewer, backend-reviewer, frontend-reviewer).
- CLI `agenthub skills install`, `agenthub lanes agents install`,
  `agenthub ship-full|ship-quick`; routes POST /api/skills/install and
  POST /api/lanes/:id/agents/install; the Settings button, the lane Tools
  menu item and the Add-lane setup step that called them.
- The Superpowers auto-install: server/lib/skill-plugins.js, the bootstrap's
  autoInstallSkillPlugins / skillPluginsSettled gate and the doctor row.

Pipelines are kept but dormant: server/data/pipelines/ is deleted, so no
template ships. `default` resolves to EMPTY_PIPELINE (no nodes, progress 0),
createLane still accepts it, POST /api/lanes/:id/stage answers 400
ENOPIPELINE, and the Workspace hides the stage timer, pickers, PipelineMap
and strip stage chip for a lane with no nodes. A template dropped into
DASHBOARD_PIPELINES_DIR turns it all back on. The server suite loads its
templates from server/__tests__/fixtures/pipelines/.

Docs: CLAUDE.md (marker, retired rules), README(.vi), INSTALL, ARCHITECTURE,
docs/LANES|PLUGINS|CLI|API, agenthub-introduction.html.

2026-09-28 17:49:05 +07:00

2.1 KiB

Raw Blame History

description

description
Diagnose a plugin-installed AgentHub — Node, npm, disk, bootstrap, server, hooks, CLI, systemd, tmux, UI build

Run the diagnostic and report what it found. Do not fix anything unless the user asks.

node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-doctor.js"

Print the output verbatim, then add at most three lines of guidance based on the FAIL and WARN rows:

FAIL Node → the installed Node is too old for node:sqlite; the server cannot start until Node is upgraded.
FAIL Hooks → duplicate hook entries double every token and cost figure. Starting a new Claude Code session removes them automatically (the bootstrap backs the file up as settings.json.agenthub-bak first).
FAIL Server → run /agenthub-update, then check ~/.claude/agenthub/runtime/bootstrap.log and server.log.
FAIL Runtime deps → the install is incomplete, not merely absent. Delete ~/.claude/agenthub/runtime/node_modules before running /agenthub-update; reinstalling over the broken tree is what let it survive.
FAIL npm or FAIL Disk → nothing else in the report can be trusted until these are fixed; both silently truncate installs.
WARN agenthub CLI → print the exact export PATH=... line from the output.
WARN systemd → when it says the unit names a previous plugin version, the dashboard is running now but will NOT come back after a reboot. Starting a new Claude Code session repairs it; print the --force command from the output as the immediate fix. "installed but not running" just needs systemctl --user start agenthub.
WARN tmux → only the run console, agenthub lanes shell and the session-reload keystrokes are affected; monitoring, lanes and the CLI are not. Print the install command from the output. If the row says ok but Start Run still fails, the server has a different PATH than this check — ask it directly with curl -s localhost:4820/api/run/tmux.
WARN Dashboard UI → run /agenthub-open to build the bundle. When the row quotes a build error, report that error — it is the actual problem.

No preamble, no summary of things that passed.

2.1 KiB Raw Blame History

2.1 KiB

Raw Blame History