assigned-review-chain
Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.
git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge /tmp/assigned-review-chain && cp -r /tmp/assigned-review-chain/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.coder/skills/assigned-review-chain ~/.claude/skills/assigned-review-chainSKILL.md
# Assigned Review Chain Use this skill only when the node task names one assigned Reviewer. The only Coder terminal status enum is `done|blocked|needs_rework`. ## Submit After implementation and verification, run exactly once per bounded review hop: ```bash command ask --chain --artifact-reply <assigned-reviewer> <<'EOF' Node: <node id> Workgroup: <workgroup id> Visible workspace identity: <controller-assigned workspace identity> Canonical node work packet ref: <ref> Allowed paths: - <project-relative path> Acceptance refs: - <ref> Verification refs: - <ref> Verification results: - <command and result> Changed paths: - <path> Blockers: - <none or exact blocker> Review the current node against the supplied work packet and acceptance refs. Your first non-empty reply line must be exactly one of: - status: pass - status: rework_required - status: blocked - status: non_converged Do not put a preamble or code fence before that machine line. EOF ``` Replace `<assigned-reviewer>` with the literal Reviewer name supplied in the node task. It is not an environment variable and must not be inferred. The machine-line requirement is part of every Reviewer request; do not rely on the Reviewer's remembered role instructions alone. Then stop. Do not poll, watch, ping, wait, or set a timeout. ## Continuation - `status: pass`: return Coder terminal `done` immediately. - `status: rework_required`: apply only the requested bounded repair, rerun verification, ask the same Reviewer with `--chain` again, then stop. - `status: blocked`: return Coder terminal `blocked`. - `status: non_converged`: return Coder terminal `needs_rework`. - `status: rework_required` remains bounded intermediate evidence only. ## Boundaries - The same assigned Reviewer is the only allowed target for every bounded review hop. - Do not use plain ask, `--silence`, multiple targets, another role, or another CCB command. - Do not claim `done` before Reviewer pass. - Do not create commits, integrate, promote, write task/runtime authority, or release agents.
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.
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 and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.
Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.
Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work going after provider/API failure.
Send a request to a CCB agent with `ask`.
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.