القائمة
Investigate stuck runs and execution failures by tracing Symphony logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
Use Symphony's linear_graphql client tool for raw Linear GraphQL operations such as comment editing, state transitions, and uploads.
Pull latest origin/main into the current branch and resolve merge conflicts. Use when Codex needs to sync a feature branch with origin before pushing.
Push current branch to origin and create or update the PR; use when asked to push, publish updates, or create a pull request.
Set up, configure, run, and troubleshoot symphony-go — an autonomous agent orchestrator that polls Linear issues and runs Codex sessions. Use when the user asks to install symphony, create a WORKFLOW.md, configure Linear integration, start the orchestrator, debug stuck agents, fix failing hooks, tune retry/backoff, set up workspaces, or any task related to running symphony-go in a repository.
| name | debug |
| description | Investigate stuck runs and execution failures by tracing Symphony logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly. |
issue_identifier: human ticket key (e.g., ENG-44)issue_id: Linear UUIDsession_id: Codex thread-turn pair (<thread_id>-<turn_id>)issue_identifier.session_id from matching lines.session_id across start, stream, completion/failure, and stall handling.# Search by ticket key
rg -n "issue_identifier=ENG-44" /path/to/logs
# Pull session IDs for that ticket
rg -o "session_id=[^ ;]+" /path/to/logs | sort -u
# Trace one session end-to-end
rg -n "session_id=<thread>-<turn>" /path/to/logs
# Focus on stuck/retry signals
rg -n "stalled|scheduling retry|turn_timeout|turn_failed|session failed" /path/to/logs
| Pattern | Cause |
|---|---|
stalled.*restarting with backoff | No codex activity beyond stall_timeout_ms |
session failed | App-server startup error |
turn_failed / turn_cancelled | Turn execution failure |
agent failed.*scheduling retry | Worker error, will retry with backoff |
| Repeated dispatch + immediate failure | Config error or workspace issue |
If the HTTP server is running, check /api/v1/state for current running sessions and retry queue state. Check /api/v1/issues/<identifier> for issue-specific debug info.