github-actions-troubleshooting
Troubleshoot GitHub Actions workflows, particularly for Go projects. Diagnose failing workflows, distinguish between code and environment issues, interpret logs, and apply fixes for common CI/CD problems.
Best use case
github-actions-troubleshooting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Troubleshoot GitHub Actions workflows, particularly for Go projects. Diagnose failing workflows, distinguish between code and environment issues, interpret logs, and apply fixes for common CI/CD problems.
Teams using github-actions-troubleshooting should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-actions-troubleshooting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-actions-troubleshooting Compares
| Feature / Agent | github-actions-troubleshooting | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Troubleshoot GitHub Actions workflows, particularly for Go projects. Diagnose failing workflows, distinguish between code and environment issues, interpret logs, and apply fixes for common CI/CD problems.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GitHub Actions Troubleshooting Skill Use the `gh` CLI and Git to diagnose and fix GitHub Actions workflow failures, particularly for Go projects. This skill helps identify whether failures are due to code issues or environment/configuration problems. ## Workflow Analysis Check the status of recent workflow runs: ```bash gh run list --repo owner/repo --limit 10 ``` View details of a specific failing workflow: ```bash gh run view <run-id> --repo owner/repo ``` Get logs for failed jobs only: ```bash gh run view <run-id> --repo owner/repo --log-failed ``` ## Distinguishing Issue Types 1. **Code Issues**: Failures in compilation, tests, or linting that occur consistently across environments 2. **Environment Issues**: Problems with dependency resolution, tool installation, or type-checking in CI that work locally ## Common Go CI Fixes ### Linter Configuration Issues - Look for "undefined" reference errors that indicate import resolution problems - Try minimal linter configs that disable type-checking linters - Use `golangci-lint run --disable-all --enable=gofmt` for basic syntax checking ### Dependency Resolution - Verify go.mod and go.sum are consistent - Run `go mod tidy` to resolve dependency conflicts - Check that required dependencies are properly declared ## Diagnostic Commands Check specific workflow job logs: ```bash gh run view --job <job-id> --repo owner/repo ``` Download workflow artifacts for inspection: ```bash gh run download <run-id> --repo owner/repo ``` ## Troubleshooting Workflow 1. Identify which jobs are failing and which are passing 2. Examine error messages for clues about the nature of the issue 3. Determine if the issue is reproducible locally 4. Apply targeted fixes based on issue type 5. Monitor subsequent workflow runs to verify resolution
Related Skills
github-kb
Manage a local GitHub knowledge base and provide GitHub search capabilities via gh CLI. Use when users ask about repos, PRs, issues, request to clone GitHub repositories, explore codebases, or need information about GitHub projects. Supports searching GitHub via gh CLI and managing local KB with GITHUB_KB.md catalog. Configure via GITHUB_TOKEN and GITHUB_KB_PATH environment variables.
sending-reactions
Emoji reactions and thinking indicators for XMTP agents. Use when adding reactions to messages or showing processing state with thinking emoji. Triggers on emoji reactions, thinking indicator, or message acknowledgment.
handling-transactions
Token transactions and wallet integration for XMTP agents. Use when sending USDC, creating transaction requests, or handling transaction confirmations. Triggers on USDC transfer, wallet calls, or transaction reference.
creating-inline-actions
Interactive button-based UI for XMTP agents following XIP-67. Use when creating menus, confirmation dialogs, selection options, or any button-based interaction. Triggers on inline actions, buttons, menus, or ActionBuilder.
super-github
**The ultimate GitHub automation framework.** Combines the best of GitHub skills for issues, PRs, releases.
<!-- https://github.com/gillberto1/moltwallet -->
---
github-mentions
Monitor and track GitHub mentions for your username across your orgs. Queries for new mentions, tracks status (pending/in_progress/completed) to avoid redundant work. Use to check for new mentions or mark mentions as being addressed.
github-pr
Fetch, preview, merge, and test GitHub PRs locally. Great for trying upstream PRs before they're merged.
github-pat
Interact with GitHub using Personal Access Tokens. Secure, user-controlled access - no OAuth, no full account access. Clone, push, branch, PR, issues. Use when user wants to work with GitHub repos.
github-issues
Fetch and manage GitHub issues via the API
flatnotes-tasksmd-github-audit
Thoroughly audit Tasks.md +.
read-github
Read GitHub repos the RIGHT way - via gitmcp.io instead of raw scraping. Why this beats web search: (1) Semantic search across docs, not just keyword matching, (2) Smart code navigation with accurate file structure - zero hallucinations on repo layout, (3) Proper markdown output optimized for LLMs, not raw HTML/JSON garbage, (4) Aggregates README + /docs + code in one clean interface, (5) Respects rate limits and robots.txt. Stop pasting raw GitHub URLs - use this instead.