claude/skills/gh-cli/SKILL.md
--- name: gh-cli description: GitHub CLI (gh) for debugging GitHub Actions and viewing releases. Use when working with: (1) GitHub Actions - view runs, check failures, download logs, re-run workflows, watch builds, (2) Releases - view, list, and download release assets. Supports JSON output for scripting and automation. --- # GitHub CLI (gh) Skill Focused guide to using GitHub CLI for debugging GitHub Actions and accessing release information. ## Authentication ```bash # Login with browser g
npx skillsauth add dededecline/dotfiles claude/skills/gh-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Focused guide to using GitHub CLI for debugging GitHub Actions and accessing release information.
# Login with browser
gh auth login
# Check authentication status
gh auth status
# Switch between accounts
gh auth switch
# List recent workflow runs
gh run list
# List runs with limit
gh run list --limit 50
# List runs by status
gh run list --status failure
gh run list --status success
gh run list --status in_progress
# List runs for specific workflow
gh run list --workflow "CI"
# List runs on specific branch
gh run list --branch main
# Get JSON output for scripting
gh run list --json conclusion,name,databaseId,headBranch,createdAt,status,displayTitle
# View run summary
gh run view <run-id>
# View run in browser
gh run view <run-id> --web
# View failed logs only
gh run view <run-id> --log-failed
# View full logs
gh run view <run-id> --log
# View job details
gh run view <run-id> --job <job-id>
# Cancel a running workflow
gh run cancel <run-id>
# Re-run a workflow
gh run rerun <run-id>
# Re-run only failed jobs
gh run rerun <run-id> --failed
# Watch a run in real-time
gh run watch <run-id>
# Download run artifacts
gh run download <run-id>
# Download specific artifact
gh run download <run-id> --name artifact-name
# List workflows
gh workflow list
# View workflow details
gh workflow view <workflow-name>
# Enable/disable workflow
gh workflow enable <workflow-name>
gh workflow disable <workflow-name>
# Trigger a workflow
gh workflow run <workflow-name>
# Trigger with inputs
gh workflow run <workflow-name> --field key=value
# Get last 3 failed runs with details
gh run list --status failure --limit 3 --json conclusion,name,databaseId,headBranch,createdAt,displayTitle
# Filter by workflow name
gh run list --status failure --workflow "CI" --limit 10
# Get failure details and logs
gh run list --status failure --limit 1 | \
jq -r '.[0].databaseId' | \
xargs -I {} gh run view {} --log-failed
# List open PRs
gh pr list
# List PRs by author
gh pr list --author @me
# View PR in terminal
gh pr view <pr-number>
# View PR in browser
gh pr view <pr-number> --web
# View PR checks/status
gh pr checks <pr-number>
# Checkout a PR locally
gh pr checkout <pr-number>
# List releases
gh release list
# View specific release
gh release view <tag>
# View latest release
gh release view --latest
# Download release assets
gh release download <tag>
# Download specific asset
gh release download <tag> --pattern "*.tar.gz"
# Get JSON output
gh release list --json tagName,name,createdAt,isLatest
# View repository details
gh repo view
# View in browser
gh repo view --web
# View specific repo
gh repo view owner/repo
# Clone repository
gh repo clone owner/repo
# Get specific fields from runs
gh run list --json databaseId,conclusion,name,createdAt | \
jq '.[] | select(.conclusion == "failure")'
# Count failures by workflow
gh run list --limit 100 --json name,conclusion | \
jq 'group_by(.name) | map({name: .[0].name, failures: map(select(.conclusion == "failure")) | length})'
# Custom table format
gh run list --json conclusion,name,createdAt | \
jq -r '.[] | "\(.createdAt)\t\(.conclusion)\t\(.name)"'
# 1. List recent failures
gh run list --status failure --limit 10
# 2. View specific failure details
gh run view <run-id>
# 3. Check failed logs
gh run view <run-id> --log-failed
# 4. Re-run failed jobs
gh run rerun <run-id> --failed
# 5. Watch re-run
gh run watch <run-id>
# View current config
gh config list
# Set default repository for session
export GH_REPO="owner/repo"
GH_TOKEN - Authentication tokenGH_REPO - Default repository (owner/repo)GH_HOST - GitHub Enterprise hostGITHUB_TOKEN - Alternative to GH_TOKEN--json field1,field2 for structured dataGH_REPO environment variable for frequently used reposgh run watch to monitor CI/CD--status, --workflow, --branch) before piping to jqgh run download to get build artifacts for debugginggh help # General help
gh <command> --help # Command-specific help
development
Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.
development
Generate PDFs from Markdown on macOS using pandoc + BasicTeX (xelatex). Use when the user asks to convert a markdown file to PDF, "export to PDF", "make a PDF of this doc", render markdown as a printable/shareable document, or any markdown→PDF conversion. Handles Unicode characters (arrows ↔, →, em-dashes —), GitHub-style lists without preceding blank lines, and ensures bullets render correctly.
development
--- name: security-review description: Security-focused code review for identifying high-confidence vulnerabilities in code changes. Use when working with: (1) Reviewing PR or branch changes for security issues, (2) Identifying injection, auth bypass, crypto, and data exposure vulnerabilities, (3) Conducting SAST-style analysis with false positive filtering, (4) Pre-merge security audits on any codebase. --- # Security Review Comprehensive security-focused code review methodology for identifyi
tools
--- name: 1password description: Complete 1Password CLI (op) for managing secrets, credentials, and secure storage. Use when working with: (1) Retrieving passwords, API keys, and secrets from vaults, (2) Managing items, documents, and secure notes, (3) Injecting secrets into environment variables and config files, (4) Automating credential rotation and management, (5) Accessing SSH keys and certificates, (6) Vault and item CRUD operations, (7) Secret references for CI/CD pipelines, (8) User and