node-check
Verify one coder node against the assigned execution contract and return pass, rework, blocked, or non-converged evidence.
git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge /tmp/node-check && cp -r /tmp/node-check/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.code_reviewer/skills/node-check ~/.claude/skills/node-checkSKILL.md
# Node Check Use this skill when the assigned Worker supplies a bounded node review packet for its current node workspace. ## Workflow 1. Bind the review to supplied provider-visible node/workgroup identity, controller-supplied workspace identity/ref, base/head commits, changed and allowed paths, acceptance refs, verification refs/results, and blockers. Missing or mismatched visible identity is `blocked`. 2. Canonical tree digest is dispatcher/controller-only route evidence checked outside provider prose. Do not cite, supply, attest, or infer it: Reviewer model text can never satisfy that check. 3. Read the supplied canonical node work packet, coder result, and dependency evidence. 4. Check that every changed path is allowed and that no scope violation or undeclared dependency exists. 5. Evaluate the supplied verification evidence. Use only read-only checks that cannot mutate the reviewed tree; otherwise report the missing proof. 6. Audit hidden fallback, degradation, scope shrinkage, and missing evidence. 7. Return a parser-stable machine verdict as the first non-empty line: `status: pass`, `status: rework_required`, `status: blocked`, or `status: non_converged`. Put explanatory evidence after that line. ## Boundaries - Do not approve contract-free work. - Do not convert partial work into success. - Do not edit files, apply fixes, create commits, integrate nodes, promote project-root state, or submit downstream asks. - Do not directly edit authoritative CCB state or runtime files. - Do not run `ccb`, `ccb_test`, or workflow wrappers. - You cannot mark the task or round done. - Provider and model selection remain project configuration concerns. This RolePack is provider-neutral and must not assume a specific provider.
Send a request to a CCB agent with `ask`.
Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.
Execute one scoped implementation or investigation item and return evidence without changing workflow authority.
Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.
Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, callback not continuing, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.
Compact CCB managed agent conversation context with `ccb compact`. Use when the user writes `$ccb-compact`, `$ccb_compact`, or asks to summarize one or more mounted agent contexts without restarting agents or deleting project state.
Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.
Diagnose a named CCB agent by combining authoritative runtime and job lineage with deep read-only pane inspection, apply bounded recovery when evidence supports it, verify the result, and request authorization before submitting a redacted GitHub issue. Use for `$ccb_diagnose agentname`, `$ccb-diagnose agentname`, or reports that a CCB agent is stuck, disconnected, not continuing, not replying, or showing provider errors.