Immutable solution version
Buddy: debugging a failed execution - read failed action logs before retrying
Complete solution
Buddy: debugging a failed execution - read failed action logs before retrying: : the order is buddy executions failed for the failed action logs, then buddy executions show with the logs flag for all actions (the verbose flag surfaces errors from skipped actions), then failed with the analyze flag for error pattern analysis.
When it applies
Not specified by the original author.
Instructions
[jtsternberg/buddy-cli]: the order is buddy executions failed for the failed action logs, then buddy executions show with the logs flag for all actions (the verbose flag surfaces errors from skipped actions), then failed with the analyze flag for error pattern analysis. For targeted debugging, use executions actions to find the specific action's hex ID, then action-logs to fetch just that one action, which is faster than pulling all logs sequentially. URL execution IDs are hex hashes and the CLI resolves them automatically. Only suggest fixes or retry after reading the logs.
Context: The fastest Buddy debugging loop reads the failed action's own logs first, then the full log, then analyzes the error pattern. Never guess before reading logs.
Matched source
Source: Source: https://github.com/jtsternberg/buddy-cli/blob/HEAD/claude-plugin/skills/troubleshooting-pipelines/SKILL.md Original query: "Buddy: debugging a failed execution - read failed action logs before retrying" Key terms: action, before, buddy, debugging, execution, failed, logs, read, retrying
Evidence
Source: The fastest Buddy debugging loop reads the failed action's own logs first, then the full log, then analyzes the error pattern. Never guess before reading logs.
Verified resolution: [jtsternberg/buddy-cli]: the order is buddy executions failed for the failed action logs, then buddy executions show with the logs flag for all actions (the verbose flag surfaces errors from skipped actions), then failed with the analyze flag for error pattern analysis. For targeted debugging, use executions actions to find the specific action's hex ID, then action-logs to fetch just that one action, which is faster than pulling all logs sequentially. URL execution IDs are hex hashes and the CLI resolves them automatically. Only suggest fixes or retry after reading the logs.
Source URL: https://github.com/jtsternberg/buddy-cli/blob/HEAD/claude-plugin/skills/troubleshooting-pipelines/SKILL.md
By @issueatlas · Version 2 · Exact version
Maintainer review
Checking maintainer review for this exact version…
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_hkf9-NSX9qUMK4v7nhL_Sg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Buddy: debugging a failed execution - read failed action logs before retrying <span>— Vectle</span></a>