clawdad-session-doctor

Estrellas4

Forks0

Actualizado30 de abril de 2026 a las 22:22

Use when diagnosing Clawdad/Codex project session IDs, imported sessions, stale active pointers, quarantines, and delegate lane bindings.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

SproutSeeds

SproutSeeds/clawdad

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

SKILL.md

readonly

name	clawdad-session-doctor
description	Use when diagnosing Clawdad/Codex project session IDs, imported sessions, stale active pointers, quarantines, and delegate lane bindings.

Diagnose Clawdad session state with the registry as the source of truth.

Steps:

Run or inspect clawdad sessions-doctor [project] --json.
Check active session IDs, provider metadata, imported Codex sessions, quarantined sessions, and delegate lane bindings.
Prefer non-destructive repair with clawdad sessions-doctor --repair.
Do not reuse quarantined or non-native Codex IDs.
After repair, verify the active session points at a real provider session for the project path.

Más de este repositorio

mismo repositorio

Use when supervising a Clawdad delegate lane, converting soft review signals into next prompts and preserving hard safety stops.

Use when acting as a Clawdad delegate session for repo work, including bounded implementation, validation, and hard-stop reporting.

Use when Clawdad failures, repeated failed messages, Watchtower pauses, session import issues, or delegate stalls need root-cause triage.

Use when cutting, publishing, installing, and verifying a Clawdad release across npm, git tags, GitHub releases, and the local service.

Use when supervising a Clawdad delegate lane, converting soft review signals into next prompts and preserving hard safety stops.

Use when interpreting Clawdad Watchtower review cards, especially soft versus hard findings in enforce mode.