health-controller-stub-detector

What problem does it solve?

This Skill prevents broken health/status integrations from being mistaken as valid system readiness by surfacing hard-coded placeholder literals like pending-integration, not-implemented, or stub in health controllers.

Core Features & Use Cases

• Detects placeholder health literals in added lines for health/status/liveness/readiness indicators to reveal contract gaps early.
• Guides operator disposition by requiring one of: implement now, defer with explicit TODO/backlog, or document out-of-scope.
• Reduces false confidence during QA gates by ensuring wish gating and downstream checks do not treat stub values as real wire-up proof.
• Use case: A team merges an upstream controller change while the downstream health-reporter isn’t wired yet, and automated gates incorrectly pass—this Skill forces early surfacing so compliance and request-flow verification don’t complete on placeholder data.

Quick Start

Run the health-controller-stub-detector gate during your /dr-do Step 7 implementation notes when your changes touch health or status controller files.