GitHub CI Fix Debugging Agent Skill
Debug and fix failing GitHub PR checks by inspecting GitHub Actions logs, summarizing failure context, drafting fix plans, and implementing fixes after approval.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/PramodDutta/qaskills --skill GitHub CI Fix DebuggingThe instruction itself
16 sections, as written by the authorGitHub CI Fix Debugging
Use gh CLI to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure, propose a fix plan, and implement after explicit approval.
Prerequisites
Authenticate with the GitHub CLI:
gh auth login # Ensure repo + workflow scopes
gh auth status # Verify authentication
Workflow
1. Verify Authentication
gh auth status
If unauthenticated, ask the user to run gh auth login with repo + workflow scopes.
2. Resolve the PR
# Current branch PR
gh pr view --json number,url
# Or use a specific PR number
gh pr checks <pr-number>
3. Inspect Failing Checks
# List all PR checks with status
gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow
# For each failing check, get the run details
gh run view <run_id> --json name,workflowName,conclusion,status,url
# Fetch the logs
gh run view <run_id> --log
4. Scope Non-GitHub Actions Checks
- If
detailsUrlis not a GitHub Actions run, label it as external - Only report the URL for external providers (Buildkite, etc.)
5. Summarize Failures
For each failing check, provide:
- The failing check name
- The run URL
- A concise log snippet showing the actual failure
- Root cause analysis
6. Create a Fix Plan
Draft a concise plan including:
- What failed and why
- Proposed fix with specific file changes
- Impact assessment
- Request explicit approval before implementing
7. Implement After Approval
- Apply the approved plan
- Summarize diffs and changes made
- Run relevant tests locally if possible
8. Recheck Status
# After fixes, verify checks pass
gh pr checks <pr>
Common CI Failure Patterns
Test Failures
- Check test output for assertion errors
- Look for environment-specific issues
- Verify test data and fixtures
Build Failures
- Check dependency versions and lockfiles
- Verify TypeScript/compilation errors
- Check for missing environment variables
Lint/Format Failures
- Run linter locally to reproduce
- Apply auto-fix where possible
- Check for new rule violations
Timeout Issues
- Identify slow tests or builds
- Check for infinite loops or deadlocks
- Consider increasing timeout or optimizing
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take pramoddutta/github ci fix debugging from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.