kbarendrecht

architecture-health-check

Read-only architecture health check for orchd — find where many individually reasonable changes have gradually degraded the architecture (responsibility accumulation, workflow fragmentation, conditional sprawl, boundary violations, unclear state ownership, incremental duplication, over-stretched abstractions). Produces a prioritized, evidence-backed report and modifies no code. Use for a periodic review, or after a subsystem has grown a lot. Optionally pass a path, subsystem, or git range to scope it.

domain-consistency-review

Read-only product & domain consistency review for orchd — reconstruct the domain model from the implementation, then check whether the domain logic is internally coherent. Finds contradictions, unclear state ownership, impossible states, duplicated business rules, and rules enforced in one place but bypassed in another — especially across the SPA / daemon / persistence / GitHub / background-poller boundaries. Produces inferred domain rules plus evidence-backed inconsistencies and modifies no code. Use to sanity-check that the product makes sense as a system, not to review code quality or architecture. Optionally pass a path or subsystem to scope it.

green

Get a PR green. Rebase it on its base branch, fix the easy red, ask about the rest, amend into the commit that owns the change, force-push, and watch CI until it passes. Use when a PR is red or has fallen behind, and never for review threads, which are somebody's words rather than a failing check.

handle-review

Work through a pull request's review threads in a pane — judge each one, apply what is right, ask about the rest, draft replies and post only on an explicit go. Use when somebody asks you to resolve, handle or answer the review feedback on a PR.

orch

How to reach the orchestrator you are running inside — ask the human a blocking question, start or end another session, list the sessions and where they run, or start one of the workspace's declared processes. Use whenever you need a decision from the person watching, want a second session to work in parallel, or need to know what else is running before touching a branch or a worktree.

review

Answer a pull request's review threads end to end with a human deciding in the orchestrator's overlay — read the threads and propose options, make the changes they pick, then post the replies. Use when the orchestrator starts a review session, or when somebody asks you to work a PR's review feedback with the overlay driving.