ccb-diagnose

Solid

Diagnose a named CCB managed agent using runtime, job-lineage, and provider evidence.

AI & Automation 3,494 stars 341 forks Updated 2 days ago NOASSERTION

Install

View on GitHub

Quality Score: 84/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
39
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# CCB Diagnose Diagnose exactly one current mounted agent. Start with CCB authority: ```bash command ccb ping "$AGENT" command ccb ps command ccb queue --detail "$AGENT" command ccb pend --inbox --detail "$AGENT" ``` Use `ccb trace` for a current lineage id and `ccb doctor logs` for provider/API evidence. For DSH, the pane is only the managed host process/log surface: pane text is not prompt, reply, or completion authority. Native authority is the exact DSH session/RPC event history and `turn/end` reason recorded by CCB. Do not read credentials, mutate tmux directly, restart all agents, or submit a GitHub issue without showing a redacted proposal and receiving explicit authorization. Apply only a bounded supported repair, then re-check the same runtime and lineage evidence.

Details

Author
SeemSeam
Repository
SeemSeam/claude_codex_bridge
Created
10 months ago
Last Updated
2 days ago
Language
Python
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category