GitHub Actions Troubleshooting
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent for troubleshooting GitHub Actions, though it can use your GitHub CLI access to view or download workflow logs and artifacts.
Install only if you want the agent to use gh and git for the selected repository. Make sure you are authenticated to the right GitHub account, review CI logs and downloaded artifacts before sharing them, and approve local file changes such as go.mod or go.sum updates.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may be able to view or download workflow information from repositories your GitHub account can access.
These commands retrieve GitHub workflow status, logs, and artifacts. The GitHub CLI normally acts with the user's GitHub account permissions, so private repository CI data may be accessed.
Use the `gh` CLI and Git to diagnose and fix GitHub Actions workflow failures ... `gh run view <run-id> --repo owner/repo --log-failed` ... `gh run download <run-id> --repo owner/repo`
Use the skill only with the intended repository and GitHub account, and avoid exposing downloaded logs or artifacts unless you have reviewed them.
The agent could create local downloaded files or change go.mod/go.sum while applying fixes.
The documented workflow includes CLI commands that can download files and modify Go dependency files. This is aligned with CI troubleshooting, but should be scoped to the intended repo and reviewed before committing changes.
Download workflow artifacts for inspection: `gh run download <run-id> --repo owner/repo` ... Run `go mod tidy` to resolve dependency conflicts
Review downloaded artifacts and inspect local file diffs before committing, pushing, or sharing any results.