/check
Health-check an existing Wakeflow workspace and converge missing or outdated Claude Code surfaces
$ npx -y skills add GxFn/Wakeflow --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/check
Context preview
What this command does when you run it.
Health-check an existing Wakeflow workspace and converge missing or outdated Claude Code surfaces
Command definition
check.mddescription: Health-check an existing Wakeflow workspace and converge missing or outdated Claude Code surfaces
argument-hint: [--fix]
Diagnose an ALREADY-INITIALIZED workspace (one that has `wakeflow.config.json`) and bring its Claude Code surfaces up to the installed plugin version. For first-time setup use `/wakeflow:init` instead.
1. Run the read-only diagnosis: `node <plugin>/scripts/lib/wakeflow-claude-host.mjs check-workspace --root <workspace>`. Render the gap report as a table (area, window, status, fix) plus the plugin-version stamp comparison. The legacy-codex-registry entry is informational only — never "fix" another host's runtime. 2. If there are no gaps, report healthy with the stamped version and stop. 3. If gaps exist and `$ARGUMENTS` does not contain `--fix`, stop after reporting with the proposed fix plan. Do not write anything. 4. With `--fix`, converge in this order, narrating each step: a. When `root-memory-file` is `unmanaged`: STOP and ask the user first — the fix replaces the existing root `CLAUDE.md` content with the managed Wakeflow gates (show its first lines). Only continue with explicit consent. b. Doc surfaces that require setup rewrite (root gates, window cards, Design/Test templates, gitignore): STOP and ask for explicit reset-initialization consent. Only after that consent, call `wakeflow_initialize_workspace` with `apply: true`, `resetInitialization: true`, explicit `repositories` copied from the confirmed `wakeflow.config.json`, and the selected Design/Test mode. Never use `useDiscovered` here. c. Permission seeds: `wakeflow-claude-host seed-permissions --root <workspace> --write`. d. Missing `hosts.claude-code` config block: merge `{ "hosts": { "claude-code": { "tmuxSession": "wakeflow" } } }` into `wakeflow.config.json` (preserve all other keys). e. Unregistered, dead, or context-heavy windows: converge each via the `/wakeflow:windows <window>` rules; use `/wakeflow:windows <window> --replace` when a fresh single-window context is needed, then `arrange-windows`. f. Stamp the converged version: `wakeflow-claude-host stamp-runtime --root <workspace> --write`. 5. Re-run `check-workspace` and report the before/after gap counts. Anything still failing is a finding to surface, not to hide.
This command never deletes state, never touches Codex-owned surfaces (`AGENTS.md`, `hosts/codex/`), and never sends task deliveries.
Notes on the converged settings layout: the COMMITTED `.claude/settings.json` of each window directory carries portable content only (allow rules plus a RELATIVE `additionalDirectories` parent reference); machine-local items — the wakeflow statusline command with its absolute script path — live in `.claude/settings.local.json`, which is never committed. `seed-permissions` migrates any older absolute-path or statusLine residue out of the committed file automatically and leaves user-custom statusLine configs untouched. The `plugin-version` gap means the workspace was last converged by an older plugin: running the fix flow re-runs seeding and `stamp-runtime` to record the current version.
Read more
description: Health-check an existing Wakeflow workspace and converge missing or outdated Claude Code surfaces argument-hint: [--fix]
Diagnose an ALREADY-INITIALIZED workspace (one that has `wakeflow.config.json`) and bring its Claude Code surfaces up to the installed plugin version. For first-time setup use `/wakeflow:init` instead.
1. Run the read-only diagnosis: `node <plugin>/scripts/lib/wakeflow-claude-host.mjs check-workspace --root <workspace>`. Render the gap report as a table (area, window, status, fix) plus the plugin-version stamp comparison. The legacy-codex-registry entry is informational only — never "fix" another host's runtime. 2. If there are no gaps, report healthy with the stamped version and stop. 3. If gaps exist and `$ARGUMENTS` does not contain `--fix`, stop after reporting with the proposed fix plan. Do not write anything. 4. With `--fix`, converge in this order, narrating each step: a. When `root-memory-file` is `unmanaged`: STOP and ask the user first — the fix replaces the existing root `CLAUDE.md` content with the managed Wakeflow gates (show its first lines). Only continue with explicit consent. b. Doc surfaces that require setup rewrite (root gates, window cards, Design/Test templates, gitignore): STOP and ask for explicit reset-initialization consent. Only after that consent, call `wakeflow_initialize_workspace` with `apply: true`, `resetInitialization: true`, explicit `repositories` copied from the confirmed `wakeflow.config.json`, and the selected Design/Test mode. Never use `useDiscovered` here. c. Permission seeds: `wakeflow-claude-host seed-permissions --root <workspace> --write`. d. Missing `hosts.claude-code` config block: merge `{ "hosts": { "claude-code": { "tmuxSession": "wakeflow" } } }` into `wakeflow.config.json` (preserve all other keys). e. Unregistered, dead, or context-heavy windows: converge each via the `/wakeflow:windows <window>` rules; use `/wakeflow:windows <window> --replace` when a fresh single-window context is needed, then `arrange-windows`. f. Stamp the converged version: `wakeflow-claude-host stamp-runtime --root <workspace> --write`. 5. Re-run `check-workspace` and report the before/after gap counts. Anything still failing is a finding to surface, not to hide.
This command never deletes state, never touches Codex-owned surfaces (`AGENTS.md`, `hosts/codex/`), and never sends task deliveries.
Notes on the converged settings layout: the COMMITTED `.claude/settings.json` of each window directory carries portable content only (allow rules plus a RELATIVE `additionalDirectories` parent reference); machine-local items — the wakeflow statusline command with its absolute script path — live in `.claude/settings.local.json`, which is never committed. `seed-permissions` migrates any older absolute-path or statusLine residue out of the committed file automatically and leaves user-custom statusLine configs untouched. The `plugin-version` gap means the workspace was last converged by an older plugin: running the fix flow re-runs seeding and `stamp-runtime` to record the current version.
A disciplined control loop for multi-window agent work — every step traced, every result reviewable.
Repo: GxFn/Wakeflow
Other commands on wakeflow.
- /dispatch
Prepare and send one Wakeflow delivery to a target window session (controller only)
Open command - /init
Initialize the current workspace as a Wakeflow control workspace (dry-run first, apply after confirmation)
Open command - /review
Inspect Wakeflow target review inputs, independently validate behavior, and record an explicit controller decision
Open command - /status
Show Wakeflow workspace status — demands, eligible work, deliveries, and window readiness
Open command - /unattended
Turn unattended (prompt-free) mode for the work windows on or off, then reopen them
Open command - /windows
List, launch, resume, or attach Wakeflow tmux windows, choosing the permission mode
Open command

