condux-doctor
Health check for the condux plugin on the host it is installed on. Runs the SessionStart routing hook on both hosts and checks each wire format, confirms Codex's hooks flag is on and plan-review's Stop hook resolves, checks the OpenCode registration and its bundled agents and skills, verifies the five specialist agents shipped, compares the installed version against the marketplace clone, and flags conflicting skill libraries installed. Offline; read-only unless --fix. Checking whether condux itself works on this machine: is condux working, the routing rule stopped appearing, /workflow is not being reached, did the SessionStart hook fire, check my condux install, the agents are missing, does condux clash with another workflow plugin. Run it after installing or updating. Not for routing a dev task (that is workflow); not for diagnosing this repo's own build or dist drift (that is toolkit-debugging-playbook).
- License 许可
- MIT
- 最近更新
- 2026-11-03
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- condux-doctor
- description
- Health check for the condux plugin on the host it is installed on. Runs the SessionStart routing hook on both hosts and checks each wire format, confirms Codex's hooks flag is on and plan-review's Stop hook resolves, checks the OpenCode registration and its bundled agents and skills, verifies the five specialist agents shipped, compares the installed version against the marketplace clone, and flags conflicting skill libraries installed. Offline; read-only unless --fix. Checking whether condux itself works on this machine: is condux working, the routing rule stopped appearing, /workflow is not being reached, did the SessionStart hook fire, check my condux install, the agents are missing, does condux clash with another workflow plugin. Run it after installing or updating. Not for routing a dev task (that is workflow); not for diagnosing this repo's own build or dist drift (that is toolkit-debugging-playbook).
- argument-hint
- [--host claude|codex|opencode] [--fix]
02 资源文件 4
- 参考文档conflicts.json3.5 KB
- 脚本conflicts.mjs7.3 KB
- 脚本doctor.mjs21.1 KB
- 参考文档evals/trigger_eval.json1.7 KB
03 SKILL.md 正文
/condux-doctor
Answers one question: is condux actually working on this host?
node <skill-base>/doctor.mjs # every host, every probe
node <skill-base>/doctor.mjs --host codex # one host
node <skill-base>/doctor.mjs --quiet # only what is not fine
node <skill-base>/doctor.mjs --fix # run the installer, then re-probe
Exit 0 when nothing is broken, 1 when something is, 2 when the doctor cannot find condux's own hooks.
--fix performs no registration itself — it runs condux's plugin-level
install.mjs and probes again, so idempotency, backups and atomic writes stay
in one place. If the installer fails, the report says how it failed rather than
re-probing in silence, and the re-probe still decides the exit code. Without an
installer beside the plugin (an npx skills add tree has none), it says so and
changes nothing.
Reading the report
One row per probe: host status detail, fix on an indented continuation
line. done works · broken needs the fix · absent is not there and not a
failure · skipped deliberately needs nothing · warn works but something
else on the machine competes with it. Only broken affects the exit code.
What it probes
- The SessionStart routing hook, by running it. Claude Code must get a
hookSpecificOutputenvelope carrying non-empty context; Codex must get the raw routing payload. Each host's manifest must use its own root variable —${CLAUDE_PLUGIN_ROOT}or${PLUGIN_ROOT}, never the other. - Codex's
features.hooksflag, before anything else on that host. A plugin manifest can declare hooks; nothing in a plugin can enable them. With the flag off, the manifest parses, every path resolves, and no hook fires — which this doctor scoreddoneuntil it learned to read the flag. It proves the flag is set, not that Codex has restarted since. - plan-review's Codex Stop hook — resolved, never executed. It blocks a turn for up to four days waiting on a human by design.
- OpenCode —
@jabworks/conduxin the plugin array, and when a local copy exists, that it ships its bundledagents/andskills/and that the routing reminder it injects names the OpenCode verb,skill(name="workflow")— a payload still saying/condux:workflowis the docket #72 under-firing shape, reported broken with an upgrade as the fix. - The five specialist agents —
coder,explorer,planner,researcher,scout. They live in a plugin-level directory reached by its own sync step, which is exactly the mirror that drifted once before. - Version — installed against the local marketplace clone, with that clone's own last-fetch date printed beside it. Never fetches.
- Conflicting skill libraries — anything in
conflicts.jsonthat is already on this machine, matched by name against the host plugin registrations and the loose skill directories. Entries are libraries that register a competingSessionStartrouter. Reportedwarn, neverbroken: condux is fine, and the removal command is printed rather than run.
Why running the hook matters
session-start.mjs fails open on purpose: if its payload is missing it exits
0 and prints nothing, because a hook that breaks the session is worse than a
hook that does nothing. Every static check passes in that state. Only
executing it reveals that condux's routing rule is silently absent — which is
the difference between /workflow being the entry point and being a lucky
guess from the catalog.
What it cannot prove
That the host invoked the hook. Nothing readable from a child process says whether Claude Code or Codex loaded a registration this session. If every probe is green and the routing rule still never appears, the fault is host-side and this report is the evidence.
Boundaries
Routing an actual dev task is workflow. Problems with this repo's build —
dist drift, a manifest that will not parse, a skill that will not trigger —
belong to toolkit-debugging-playbook: that one needs the source tree, this
one needs only the install.
04 同仓库更多 Skills
orphan
暂无简介
no-blurb
暂无简介
workflow
Routes any dev task into the right execution tier (Small/Medium/Large) and carries condux's operating rules — proportional effort, lazy skill loading, soft gates, implement-yourself-by-default.
usage-trace
Checks and manages durable, local usage capture — ingest, health status, and the opt-in limit snapshot — for Claude Code and Codex. Capture itself runs automatically at session start.
toolkit-skill-standards
Use when writing or reviewing a SKILL.md for jabworks/agentic-toolkit — frontmatter budgets, the trigger contract ("Use when…" description or when_to_use field), progressive disclosure into references/, and keeping a new description out of existing skills' trigger space. Triggers include "review this skill description", "write the frontmatter", "does this collide with an existing skill", "where should this content live". Not for scaffold/sync mechanics; use toolkit-foundry.
toolkit-research-frontier
Use when planning improvement work on jabworks/agentic-toolkit itself — open problems (trigger-collision automation, YAML-strict frontmatter checks, docs-catalog enforcement), existing assets, the next three concrete steps, and the four-front library-health campaign with commands and success criteria. Triggers include "let's improve our toolkit", "let's improve this repo", "what should we improve next", "toolkit roadmap", "open problems", "run the health campaign".