What problem does it solve?
When Comet Hooks, installations, routing, or generated Runtime behavior misbehave, it is hard to tell whether the cause is stale configuration, generated asset drift, unsupported platforms, or an actual source code defect. This Skill provides a structured diagnostic workflow that separates these causes before any fix is attempted.
Core Features & Use Cases
- Problem Classification: Categorizes reports into stale installs, configuration or path ownership issues, source/Runtime defects, generated asset drift, platform registration inconsistencies, or lifecycle contract mismatches.
- Real Execution Path Verification: Runs the packaged Router or Runtime with the actual project cwd and platform identifiers instead of relying on static configuration checks.
- Cross-Platform Registry Checks: Compares affected adapters against the canonical platform registry rather than ad-hoc platform lists.
- Use Case: A maintainer receives a report that a Comet Hook fails after reinstalling. The Skill inspects installed files, generated bundles, manifests, and lifecycle JSON, then reports whether the issue is reproducible, configuration-only, drift-only, or a production defect.
Quick Start
Use the comet-runtime-diagnose skill to diagnose why my Comet Hook is not triggering after a fresh install.