interhelm

Reviews diagnostic server implementations for pattern completeness, security, and performance. Use when an agent has scaffolded a diagnostic HTTP server and CLI for a project. Examples: <example>user: "I've implemented the debug server for my Tauri app" assistant: "I'll use the runtime-reviewer agent to verify completeness, security, and performance." <commentary>New diagnostic server needs validation against all four patterns plus security and performance checks.</commentary></example> <example>user: "Review my /diag endpoints for issues" assistant: "I'll use the runtime-reviewer agent to check pattern coverage and operational quality." <commentary>Diagnostic endpoint review requires pattern completeness, security, and performance analysis.</commentary></example>

Use when verifying critical user journeys in a running application without screenshots — queries structured /diag/ui/state endpoints for semantic UI state instead of visual inspection.

Use when you have a basic diagnostic server scaffold and need to evolve it into a production-grade operator toolkit. Guides through 6 maturation levels (domain health → smoke tests → assert language → CLI formatting → diff engine → REPL+watch) with verification gates at each level. Also provides conformance audit mode to evaluate existing diagnostic servers against the maturation ladder.

Use when you need to verify a running native app works correctly after code changes, can't use browser DevTools, need to check runtime state without screenshots, or want to confirm a Tauri/Electron app's simulation or UI didn't break. Guides scaffolding of a diagnostic HTTP server with Health, Diff, Assert, Smoke Test patterns plus semantic UI state endpoint.

Use when designing end-to-end verification for a running application — teaches the executable contract pattern where smoke tests serve as the agreement between diagnostic server and CLI client.

3 hooks across 1 event