🎯

workflow

🎯Skill

from johnlindquist/claude

VibeIndex|
What it does

Efficiently manage GitHub Actions workflows by checking status, viewing logs, analyzing failures, and rerunning CI/CD processes via GitHub CLI.

πŸ“¦

Part of

johnlindquist/claude(50 items)

workflow

Installation

Install ScriptRun install script
curl -sS https://webi.sh/gh | sh
πŸ“– Extracted from docs: johnlindquist/claude
10Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

Manage GitHub Actions workflows using gh CLI. Use to check CI status, view run logs, analyze failures, and rerun workflows.

Overview

# GitHub Actions Workflow Manager

Monitor and manage CI/CD workflows using the GitHub CLI.

Prerequisites

Install GitHub CLI:

```bash

brew install gh

# or

curl -sS https://webi.sh/gh | sh

```

Authenticate:

```bash

gh auth login

```

CLI Reference

Quick Status Check

```bash

# Current branch CI status

gh run list --branch $(git branch --show-current) --limit 5

# All recent runs

gh run list --limit 10

# Filter by workflow

gh run list --workflow "CI" --limit 5

```

View Specific Run

```bash

# Get run details

gh run view

# View with logs

gh run view --log

# Failed jobs only

gh run view --log-failed

# Exit codes for CI scripts

gh run view --exit-status

```

List Runs with Filters

```bash

# By branch

gh run list --branch main --limit 10

# By workflow name

gh run list --workflow "Build and Test" --limit 10

# By status

gh run list --status failure --limit 10

gh run list --status success --limit 10

gh run list --status in_progress --limit 10

# Combined filters

gh run list --branch main --workflow "CI" --status failure --limit 5

```

Rerun Workflows

```bash

# Rerun entire workflow

gh run rerun

# Rerun only failed jobs

gh run rerun --failed

# Rerun specific job

gh run rerun --job

```

Watch Running Workflow

```bash

# Watch a run in progress

gh run watch

# Watch and exit with run's exit code

gh run watch --exit-status

```

Download Artifacts

```bash

# List artifacts from a run

gh run view --json artifacts

# Download all artifacts

gh run download

# Download specific artifact

gh run download --name "artifact-name"

# Download to specific directory

gh run download --dir ./artifacts

```

Cancel a Run

```bash

gh run cancel

```

View Workflow Files

```bash

# List workflow files

gh workflow list

# View specific workflow

gh workflow view "CI"

# Enable/disable workflow

gh workflow enable "CI"

gh workflow disable "CI"

```

Run Workflow Manually

```bash

# Trigger workflow_dispatch

gh workflow run "CI"

# With inputs

gh workflow run "Deploy" -f environment=staging -f version=1.2.3

# On specific branch

gh workflow run "CI" --ref feature-branch

```

Output Formats

```bash

# JSON output for parsing

gh run list --json status,conclusion,name,headBranch,url

# Specific fields

gh run view --json jobs,status,conclusion

```

Workflow Patterns

Quick CI Check

```bash

# Is my branch passing?

gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion

```

Debug Failing CI

```bash

# 1. Find the failing run

gh run list --branch main --status failure --limit 1

# 2. View failed logs

gh run view --log-failed

# 3. After fixing, rerun

gh run rerun --failed

```

Monitor Deployment

```bash

# Watch deployment in progress

gh run watch

# Get notified when done (macOS)

gh run watch && osascript -e 'display notification "Deployment complete"'

```

Retry Flaky Tests

```bash

# Rerun just the failed jobs

gh run rerun --failed

```

Pre-Merge Check

```bash

# Ensure all checks pass before merging

gh run list --branch $(git branch --show-current) --json conclusion --jq '.[0].conclusion'

```

Common Statuses

| Status | Meaning |

|--------|---------|

| queued | Waiting to start |

| in_progress | Currently running |

| completed | Finished |

| Conclusion | Meaning |

|------------|---------|

| success | All jobs passed |

| failure | One or more jobs failed |

| cancelled | Run was cancelled |

| skipped | Run was skipped |

| timed_out | Run exceeded time limit |

Best Practices

  1. Check status before merge - Ensure CI passes
  2. Use --log-failed - Only see relevant failure logs
  3. Rerun --failed first - Faster than full rerun
  4. Watch long runs - Don't poll manually
  5. Download artifacts - For test reports, coverage, etc.
  6. Use JSON output - For scripting and parsing