Spark
Sign In
Skill

Debug GitHub CI/CD and Pull Requests

GitHub Skill extends AI assistants with gh CLI commands to check pull request status, debug CI failures, list workflow runs, and query GitHub issues using

Get skill
Works with github
Antigravity
Maintainer?
78
Spark score
out of 100
Updated 17 days ago
Version 1.0.0
Add to Favorites

Why it matters

Automate the investigation and debugging of GitHub issues, pull requests, and CI/CD workflow failures. This skill leverages the GitHub CLI to provide detailed insights into your development pipeline.

Outcomes

What it gets done

01

Check CI status on pull requests.

02

List and view recent workflow runs.

03

Fetch logs for failed CI steps.

04

Query GitHub API for advanced data retrieval.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-github | bash

Capabilities

What this skill does

Debug

Traces errors to their root cause and suggests fixes.

Deploy / CI

Runs build pipelines, tests, and deploys to environments.

Review code

Analyzes code for bugs, style issues, and improvements.

Query a database

Writes and executes SQL or NoSQL queries on databases.

Overview

GitHub Skill

What it does

A skill that provides gh CLI commands for checking GitHub pull request status, viewing CI workflow runs, examining failed test logs, and querying GitHub issues and API data from the command line.

How it connects

Use this skill when you need to check the status of pull requests, investigate CI failures, list workflow runs, or query GitHub data without switching to a browser or separate terminal.

Source README

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

When to Use

  • When the user asks about GitHub issues, pull requests, workflow runs, or CI failures.
  • When you need gh issue, gh pr, gh run, or gh api from the command line.

Pull Requests

Check CI status on a PR:

gh pr checks 55 --repo owner/repo

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View a run and see which steps failed:

gh run view <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-id> --repo owner/repo --log-failed

Debugging a CI Failure

Follow this sequence to investigate a failing CI run:

  1. Check PR status - identify which checks are failing:
    gh pr checks 55 --repo owner/repo
  2. List recent runs - find the relevant run ID:
    gh run list --repo owner/repo --limit 10
  3. View the failed run - see which jobs and steps failed:
    gh run view <run-id> --repo owner/repo
  4. Fetch failure logs - get the detailed output for failed steps:
    gh run view <run-id> --repo owner/repo --log-failed

API for Advanced Queries

The gh api command is useful for accessing data not available through other subcommands.

Get PR with specific fields:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

JSON Output

Most commands support --json for structured output. You can use --jq to filter:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.