feedback-loop

Automating verification loops requires a structured approach to select, initialize, and monitor runtime health. This skill orchestrates these loops by maintaining a lightweight state file, tracking PID, port, and health URL to ensure a trustworthy live verification surface across web UI, CLI/TUI, and API contexts.

Managing shared runtime state for multiple devops verification loops involves tracking process lifecycle signals like PID, port, and health URL. This skill maintains a single source of truth in a lightweight state file, allowing you to detect stale loops and reuse existing processes instead of duplicating orchestration efforts.

Yes, delegating runtime ownership of a verification loop to other monitoring skills is supported. This skill provides explicit ownership delegation, allowing other verification tools to take over the runtime lifecycle while maintaining a centralized state file for health monitoring and process continuity.

Yes, this feedback loop orchestration tool requires git, jj, lsof, and curl as dependencies. These command-line utilities are utilized to manage version control state, inspect open files and ports, and perform health checks against running verification loops.

To monitor the health of a runtime verification loop using bash scripts, the system records specific health signals such as the process PID, active port, and a designated health URL. It then performs automated health checks against these endpoints to detect and clean up stale loops.

Runtime verification loops lose track of active port and process state when orchestration lacks centralized tracking. This skill solves the issue by maintaining a lightweight state file that records the PID, port, and health URL, ensuring a single source of truth for loop health and preventing stale processes.