Awesome-omni-skills gh-fix-ci

Gh Pr Checks Plan Fix workflow skill. Use this skill when the user needs a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Uses gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treats external providers (for example Buildkite) as out of scope and reports only the details URL. Do NOT use for addressing PR review comments (use gh-address-comments) or general CI outside GitHub Actions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/gh-fix-ci" ~/.claude/skills/diegosouzapw-awesome-omni-skills-gh-fix-ci && rm -rf "$T"

manifest: skills/gh-fix-ci/SKILL.md

Gh Pr Checks Plan Fix

Overview

This public intake copy packages

packages/skills-catalog/skills/(tooling)/gh-fix-ci

from

https://github.com/tech-leads-club/agent-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Gh Pr Checks Plan Fix

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Inputs.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

Use when the request clearly matches the imported source intent: a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Uses gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treats....
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`scripts/inspect_pr_checks.py`	Starts with the smallest copied file that materially changes execution
Supporting context	`LICENSE.txt`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Verify gh authentication.
Run gh auth status in the repo.
If unauthenticated, ask the user to run gh auth login (ensuring repo + workflow scopes) before proceeding.
Resolve the PR.
Prefer the current branch PR: gh pr view --json number,url.
If the user provides a PR number or URL, use that directly.
Inspect failing checks (GitHub Actions only).

Imported Workflow Notes

Imported: Workflow

Verify gh authentication.
- Run
```
gh auth status
```
  in the repo.
- If unauthenticated, ask the user to run
```
gh auth login
```
  (ensuring repo + workflow scopes) before proceeding.
Resolve the PR.
- Prefer the current branch PR:
```
gh pr view --json number,url
```
  .
- If the user provides a PR number or URL, use that directly.

Inspect failing checks (GitHub Actions only).

Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
- ```
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"
```
- Add
```
--json
```
  for machine-friendly output.

Manual fallback:

gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow

If a field is rejected, rerun with the available fields reported by
```
gh
```
.

For each failing check, extract the run id from

detailsUrl

and run:

gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headSha

```
gh run view <run_id> --log
```

If the run log says it is still in progress, fetch job logs directly:
- ```
gh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"
```

Scope non-GitHub Actions checks.
- If
```
detailsUrl
```
  is not a GitHub Actions run, label it as external and only report the URL.
- Do not attempt Buildkite or other providers; keep the workflow lean.
Summarize failures for the user.
- Provide the failing check name, run URL (if any), and a concise log snippet.
- Call out missing logs explicitly.
Create a plan.
- Use the
```
create-plan
```
  skill to draft a concise plan and request approval.
Implement after approval.
- Apply the approved plan, summarize diffs/tests, and ask about opening a PR.
Recheck status.
- After changes, suggest re-running the relevant tests and
```
gh pr checks
```
  to confirm.

Imported: Overview

Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix plan and implement after explicit approval.

If a plan-oriented skill (for example
```
create-plan
```
) is available, use it; otherwise draft a concise plan inline and request approval before implementing.

Prereq: authenticate with the standard GitHub CLI once (for example, run

gh auth login

), then confirm with

gh auth status

(repo + workflow scopes are typically required).

Imported: Inputs

```
repo
```
: path inside the repo (default
```
.
```
)
```
pr
```
: PR number or URL (optional; defaults to current branch PR)
```
gh
```
authentication for the repo host

Examples

Example 1: Ask for the upstream workflow directly

Use @gh-fix-ci to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @gh-fix-ci against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @gh-fix-ci for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @gh-fix-ci using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Quick start

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"

Add
```
--json
```
if you want machine-friendly output for summarization.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

packages/skills-catalog/skills/(tooling)/gh-fix-ci

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@accessibility
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@ai-cold-outreach
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@ai-pricing
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@ai-sdr
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/inspect_pr_checks.py`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Bundled Resources

scripts/inspect_pr_checks.py

Fetch failing PR checks, pull GitHub Actions logs, and extract a failure snippet. Exits non-zero when failures remain so it can be used in automation.

Usage examples:

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --json

python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40