comet-runtime-diagnose

Diagnose Comet Hook, installation, routing, and generated Runtime behavior against contracts.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-runtime-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-runtime-diagnose
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-runtime-diagnose
Command: npx skills add https://github.com/rpamis/comet --skill comet-runtime-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about comet-runtime-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a Comet Hook that is not working?

Classify the report first as stale install, configuration issue, source defect, or asset drift, then execute the packaged Router or Runtime with the real project cwd and platform identifier. Compare installed files, generated bundles, and lifecycle JSON against the expected contract before changing any source code.

How to tell if a Comet Runtime issue is a config problem or a code bug?

Run the real generated Runtime path rather than relying on static configuration checks. If the packaged Runtime behaves correctly with proper context, the issue is configuration or drift; if it fails reproducibly against the contract, it is a source defect.

Does the diagnostic skill modify source code or installations?

No. It only observes and reports commands, paths, expected contracts, actual results, and evidence. Source modifications, reinstalls, or GitHub issue changes happen only when the user explicitly authorizes a fix, which is handed to the comet-github-issue-fix skill.

Why does a Comet Hook behave differently across projects?

Project-level and global Hooks have different ownership scopes, and missing or ambiguous project context can change routing behavior. The diagnostic distinguishes these ownership boundaries and stays neutral when trustworthy host context is unavailable.

What are the limitations of static configuration checks for Runtime diagnosis?

Static checks cannot confirm real execution behavior, protected versus allowed phases, or platform registration consistency. Genuine diagnosis requires invoking the generated Router or Runtime and cross-checking adapters against the canonical platform registry.