debug

Name: debug
Availability: InStock
Author: ReinaMacCredy

Analyze Symphony and Codex logs to trace AI agent run failures.

Updated Mar 13, 2026

Search Tags:#debugging #troubleshooting #logs #codex #error analysis #symphony

Ready to run

npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill debug-reinamaccredy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ReinaMacCredy/Maestro-CLI/tree/main/.codex/skills/maestro%3Asymphony-setup/reference/codex-skills/debug
Command: npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill debug-reinamaccredy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you diagnose and resolve issues when AI runs get stuck, retry endlessly, or fail unexpectedly by providing a structured way to trace logs.

Core Features & Use Cases

Log Analysis: Efficiently search and correlate Symphony and Codex logs using issue and session identifiers.
Root Cause Isolation: Pinpoint the exact stage of failure, whether it's an orchestrator loop, app-server startup, or a specific turn execution.
Use Case: When a feature development run stalls, use this Skill to quickly find the relevant session logs, identify the error, and understand why the process is not completing.

Quick Start

Use the debug skill to find logs related to issue MT-625 and trace its session ID.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I trace Symphony and Codex logs to find why an AI agent run failed?▼

Trace Symphony and Codex logs by correlating Linear issue identifiers and session IDs to find the exact execution lifecycle stage where the failure occurred. This isolates root causes in stalled orchestrator loops or specific turn executions.

What is the best way to debug stalled AI agent runs using session IDs?▼

Debugging stalled AI agent runs involves searching logs with session IDs to trace the execution lifecycle and isolate root causes. This pinpoints whether failures occur during app-server startup, orchestrator loops, or specific turn executions.

Do I need grep or ripgrep to analyze Symphony and Codex logs for failures?▼

You need grep or ripgrep installed to analyze Symphony and Codex logs for failures. These tools provide the efficient multi-file searching required to correlate Linear issue identifiers and session IDs across large log datasets.

Can I correlate Linear issue identifiers with Codex logs to isolate root causes?▼

You can correlate Linear issue identifiers with Codex logs to isolate root causes of failures. By matching issue identifiers to session IDs, you trace the full execution lifecycle and pinpoint the exact stage where the process stalls.

Why does my AI feature development run stall during orchestrator loops?▼

AI feature development runs stall during orchestrator loops due to execution failures traceable in Symphony logs. By searching session IDs, you can identify the exact error stage, whether in app-server startup, orchestrator loops, or turn execution.