From kagents
GitHub Actions debugging — failed workflow analysis, error pattern diagnosis (exit codes, permissions, rate limiting, timeouts), log downloading, matrix failure isolation, gh CLI, debug re-runs. USE FOR: analyzing why a workflow run failed, diagnosing CI performance issues, reading workflow logs. DO NOT USE FOR: creating new workflows or actions (use github-actions-patterns).
npx claudepluginhub grexyloco/k.agents --plugin kagentsThis skill uses the workspace's default tool permissions.
1. Run-ID ermitteln: `gh run list --status failure --limit 5`
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
gh run list --status failure --limit 5gh run view <RUN_ID> --log-failed| Symptom | Wahrscheinliche Ursache |
|---|---|
Process completed with exit code 1 | Test/Build-Fehler im Code |
Error: Resource not accessible | Fehlende Permissions im Workflow |
Error: HttpError: rate limit exceeded | API Rate Limiting |
The runner has received a shutdown signal | Timeout oder Cancellation |
No space left on device | Artefakte/Cache zu groß |
# Welche Matrix-Kombination ist betroffen?
gh run view <RUN_ID> --json jobs --jq '.jobs[] | select(.conclusion=="failure") | .name'
gh run view <RUN_ID> --json jobs --jq '.jobs[] | {name, duration: (.completedAt | fromdate) - (.startedAt | fromdate)}'Post actions/cache Step in LogsACTIONS_STEP_DEBUG=truegh run rerun <RUN_ID> --job <JOB_ID>mxschmitt/action-tmate (nur für Debugging)