Skill

gh-cli

Guide for using the GitHub CLI (gh) to manage GitHub Actions workflows in the crewchief repository.

Install

npx claudepluginhub manifoldlogic/claude-code-plugins --plugin github-actions

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Guide for using the GitHub CLI (gh) to manage GitHub Actions workflows in the crewchief repository.

Supporting Assets

scripts/check-auth.sh

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

169.2k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

169.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

169.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitDec 2, 2025

Actions

View Source View Plugin View on GitHub View README

gh-cli

Guide for using the GitHub CLI (gh) to manage GitHub Actions workflows in the crewchief repository.

Authentication Check (CRITICAL)

Before using any gh commands, you MUST verify authentication:

gh auth status

If not authenticated, STOP and tell the user:

GitHub CLI is not authenticated. Please run gh auth login to authenticate before proceeding.

Do NOT attempt any gh commands until authentication is confirmed.

Common Workflow Commands

List Workflows

# List all workflows
gh workflow list

# List workflows with status
gh workflow list --all

View Workflow Runs

# List recent workflow runs
gh run list

# List runs for a specific workflow
gh run list --workflow=ci.yml

# List failed runs only
gh run list --status=failure

# List runs for a specific branch
gh run list --branch=main

View Run Details

# View a specific run (by ID or URL)
gh run view <run-id>

# View with job details
gh run view <run-id> --verbose

# View failed jobs
gh run view <run-id> --log-failed

Download Logs

# Download all logs for a run
gh run download <run-id>

# Download specific artifact
gh run download <run-id> --name=<artifact-name>

Trigger Workflows

# Trigger a workflow_dispatch workflow
gh workflow run <workflow-name>

# Trigger with inputs
gh workflow run <workflow-name> --field=environment=staging

Rerun Workflows

# Rerun a failed workflow
gh run rerun <run-id>

# Rerun only failed jobs
gh run rerun <run-id> --failed

Cancel Workflows

# Cancel a running workflow
gh run cancel <run-id>

Troubleshooting Failed Workflows

Check authentication first:
```
gh auth status
```
List recent failures:
```
gh run list --status=failure --limit=5
```
View failed run logs:
```
gh run view <run-id> --log-failed
```

Download full logs for analysis:

gh run download <run-id> --dir=/tmp/workflow-logs

Secrets and Variables

# List secrets (names only, not values)
gh secret list

# Set a secret
gh secret set SECRET_NAME

# List environment variables
gh variable list

Best Practices

Always check auth status before running any commands
Use --json flag for parsing output programmatically
Specify workflow by filename (e.g., ci.yml) not display name
Use --limit to reduce output when listing many items
Check PR status before and after pushing changes

Error Handling

Common errors and solutions:

Error	Solution
`gh: command not found`	Install GitHub CLI: `brew install gh` or see https://cli.github.com/
`not logged in`	Run `gh auth login`
`HTTP 401`	Re-authenticate: `gh auth login`
`HTTP 403`	Check repository permissions
`HTTP 404`	Verify workflow/run exists, check repository name

JSON Output

For programmatic use, add --json flag:

# List runs as JSON
gh run list --json status,conclusion,databaseId,workflowName

# View run as JSON
gh run view <run-id> --json jobs,status,conclusion