Gh Pr Checks Plan Fix
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
Overview
The Gh Pr Checks Plan Fix skill, hosted in the mxyhi/ok-skills repository, enables AI agents to diagnose and resolve failing GitHub Pull Request checks. By leveraging the GitHub CLI, the skill inspects check statuses and retrieves execution logs to pinpoint the root cause of CI/CD failures within GitHub Actions. After summarizing the failure context, the agent drafts a remediation plan, though implementation only proceeds following explicit user approval. While the skill is optimized for native GitHub Actions, it identifies external providers like Buildkite by reporting their detail URLs without attempting direct debugging. This tool is compatible with agents such as Codex and Claude, utilizing the popularity of its source repository to streamline automated DevOps troubleshooting workflows.
Use Cases
Install Notes
# Review source first
open https://github.com/mxyhi/ok-skills/blob/main/gh-fix-ci/SKILL.mdCopy or clone the skill folder into your agent skills directory after reviewing its instructions and scripts.
Security Notes
This skill requires GitHub CLI access and appropriate repository permissions to read logs and modify code. To maintain repository integrity, it enforces a mandatory manual approval step before any proposed fixes are implemented. Users must ensure that the AI agent environment is securely configured to manage GitHub authentication tokens.
Related Skills
CI Cd And Automation
addyosmani/agent-skills
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Observability And Instrumentation
addyosmani/agent-skills
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Core
vercel-labs/agent-browser
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multip...
Agentcore
vercel-labs/agent-browser
Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bed...
Agent Browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a butto...
Netlify Forms
openai/plugins
Guide for using Netlify Forms for HTML form handling. Use when adding contact forms, feedback forms, file upload forms, or any form that should be collected by Netlify. Covers the data-netlify attribute, spam filtering, AJAX submissions, file uploads, notifications, and the submissions API.