Workflow·Cloud & DevOps

Fix CI Failures

Analyze and fix failed GitHub Actions CI jobs for the current branch/PR.

You say
Buy it · $12 Read it before you buy $12 Written by streamlit · unverified publisher
Context cost
2.1k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 8.5 kBtext throughout, nothing executable
Licence
Apache-2.0paid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

devopsgithub
Filed under

Cloud & DevOps

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md8.5 kB · 266 lines
--- name: fixing-streamlit-ci description: Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally. ---
6# Fix CI Failures
7
8Diagnose and fix failed GitHub Actions CI jobs for the current branch/PR using [gh CLI](https://cli.github.com/manual/) and git commands.
9
10## When to Use
11
12- CI checks have failed on a PR
13- You need to understand why a workflow failed
14- You want to apply fixes and verify locally
15
16## Workflow
17
18Copy this checklist to track progress:
19
20```
21- [ ] Verify authentication
22- [ ] Gather context & find failed jobs
23- [ ] Download & analyze logs
24- [ ] Present diagnosis to user
25- [ ] Apply fix & verify locally
26- [ ] Push & recheck CI
27```
28
29### 1. Verify Authentication
30
31```bash
32gh auth status
33```
34
35If authentication fails, prompt user to run gh auth login with appropriate scopes.
36
37### 2. Gather PR Context
38
39```bash
40# Get PR for current branch
41gh pr view --json number,title,url,headRefName
42
43# Get PR description and metadata
44gh pr view --json title,body,labels,author
45
46# List changed files
47gh pr diff --name-only
48
49# All changes
50gh pr diff
51```
52
53### 3. Check CI Status
54
55```bash
56# List all checks (shows pass/fail status)
57gh pr checks
58
59# Get detailed check info
60gh pr checks --json name,state,conclusion,detailsUrl,startedAt,completedAt
61
62# List only failed runs
63gh run list --branch $(git branch --show-current) --status failure --limit 10
64
65# Check if CI is still running
66gh run list --branch $(git branch --show-current) --status in_progress
67```
68
69### 4. Find Failed Jobs
70
71```bash
72# View run details (get RUN_ID from previous step)
73gh run view {RUN_ID}
74
75# List failed jobs with IDs
76gh run view {RUN_ID} --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {id: .databaseId, name: .name}'
77
78# List failed jobs with their failed steps
79gh run view {RUN_ID} --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {name: .name, steps: [.steps[] | select(.conclusion == "failure") | .name]}'
80```
81
82### 5. Download & Analyze Logs
83
84**Primary method:**
85
86```bash
87# Get failed logs (last 250 lines usually contains the error)
88gh run view {RUN_ID} --log-failed 2>&1 | tail -250
89
90# Target a specific failed job by ID
91gh run view {RUN_ID} --job {JOB_ID} --log-failed 2>&1 | tail -100
92```
93
94**Fallback for pending logs:**
95
96```bash
97REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
98gh api "/repos/${REPO}/actions/jobs/{JOB_ID}/logs"
99```
100
101**Smart log extraction (examples):**
102
103```bash
104# Context around failure markers
105gh run view {RUN_ID} --log-failed 2>&1 | grep -B 5 -A 10 -iE "error|fail|exception|traceback|panic|fatal" | head -100
106
107# Python tests - pytest summary
108gh run view {RUN_ID} --log-failed 2>&1 | grep -E -A 50 "FAILED|ERROR|short test summary"
109
110# TypeScript/ESLint errors
111gh run view {RUN_ID} --log-failed 2>&1 | grep -E -B 2 -A 5 "error TS|error "
112
113# E2E snapshot mismatches
114gh run view {RUN_ID} --log-failed 2>&1 | grep -E -B 2 -A 5 "Missing snapshot for|Snapshot mismatch for"
115```
116
117### 6. Analyze Failure
118
119Identify:
120- **Error type**: Lint, type check, test failure, build error
121- **Root cause**: First/primary error (not cascading failures)
122- **Affected files**: Which files need changes
123- **Error message**: Exact error text
124
125**Common CI failure categories:**
126
127| Category | Workflow | Make Command | Auto-fix |
128|----------|----------|--------------|----------|
129| Python lint | python-tests.yml | make python-lint | ✅ make autofix |
130| Python types | python-tests.yml | make python-types | ❌ Manual |
131| Python tests | python-tests.yml | make python-tests | ❌ Manual |
132| Frontend lint | js-tests.yml | make frontend-lint | ✅ make autofix |
133| Frontend types | js-tests.yml | make frontend-types | ❌ Manual |
134| Frontend tests | js-tests.yml | make frontend-tests | ❌ Manual |
135| E2E tests | playwright.yml | make run-e2e-test <file> | ❌ Manual |
136| E2E snapshots | playwright.yml | make run-e2e-test <file> | ✅ make update-snapshots |
137| NOTICES | js-tests.yml | make update-notices | ✅ make update-notices |
138| Min constraints | python-tests.yml | make update-min-deps | ✅ make update-min-deps |
139| Pre-commit | enforce-pre-commit.yml | uv run pre-commit run --all-files | ✅ Mostly auto-fix |
140| Relative imports | ensure-relative-imports.yml | Check script output | ❌ Manual |
141| **PR Labels** | require-labels.yml | N/A | ⏭️ **Ignore** |
142
143> 💡 **Quick win:** Run make autofix first for lint/formatting failures.
144
145### 7. Present Diagnosis
146
147**For multiple failures**, list all and let user choose:
148
149```
150CI Failure Analysis for PR #{NUMBER}: {TITLE}
151═══════════════════════════════════════════════════════════════
152
153Found {N} failed jobs/checks:
154
155─────────────────────────────────────────────────────────────────
156
1571. [LINT] Python Unit Tests → Run Linters
158 Workflow: python-tests.yml (GitHub Actions)
159 Error: Ruff formatting error in lib/streamlit/elements/foo.py
160 Auto-fix: ✅ make autofix
161
1622. [TYPE] Javascript Unit Tests → Run type checks
163 Workflow: js-tests.yml (GitHub Actions)
164 Error: TS2322: Type 'string' is not assignable to type 'number'
165 File: frontend/lib/src/components/Bar.tsx:42
166 Auto-fix: ❌ Manual fix required
167
168─────────────────────────────────────────────────────────────────
169
170Which failures should I address?
171Recommended: "1" (auto-fixable)
172Options: "1" | "1,2" | "1-2" | "all" | "only auto-fixable"
173```
174
175**For single failure**, show detailed analysis:
176
177```
178─────────────────────────────────────────────────────────────────
179Analyzing: [TYPE] Javascript Unit Tests → Run type checks
180─────────────────────────────────────────────────────────────────
181
182Category: TYPE
183Workflow: js-tests.yml
184Job: js-unit-tests (ID: 12345678)
185Step: Run type checks
186
187Error snippet:
188 frontend/lib/src/components/Bar.tsx:42:5
189 error TS2322: Type 'string' is not assignable to type 'number'.
190
191Proposed Fix:
192 Change type annotation or fix the value type
193
194─────────────────────────────────────────────────────────────────
195
196Would you like me to:
197 [1] Apply the fix automatically
198 [2] Show the proposed changes first
199 [3] Run local verification only
200 [4] Skip this and move to next failure
201```
202
203### 8. Apply Fix & Verify Locally
204
205After user approval, apply fix and run verification:
206
207```bash
208# Run all checks (lint, types, tests) on changed files
209make check
210
211# Python tests (specific)
212uv run pytest lib/tests/path/to/test_file.py::test_name -v
213
214# Frontend tests (specific)
215cd frontend && yarn test path/to/test.test.tsx
216
217# E2E tests
218make run-e2e-test {test_file.py}
219
220# E2E snapshots
221make update-snapshots
222```
223
224### 9. Summary & Push
225
226```bash
227git status --short
228git diff --stat
229```
230
231Report what failed, what changed, and local verification result.
232
233```bash
234git add -A
235git commit -m "fix: resolve CI failure in {workflow/step}"
236git push
237```
238
239### 10. Recheck CI Status
240
241```bash
242gh pr checks --watch
243# Or re-run failed jobs
244gh run rerun {RUN_ID} --failed
245```
246
247## Rules
248
249- **Focus on root cause**: First error, not cascading failures
250- **Minimal fixes**: Smallest change that fixes the issue
251- **Don't skip tests**: Never disable tests to "fix" CI
252- **Verify locally**: Always run appropriate local command
253- **Preserve intent**: Understand what code was trying to do
254
255## Error Handling
256
257| Issue | Solution |
258|-------|----------|
259| Auth failed | gh auth login with workflow/repo scopes |
260| No PR for branch | gh run list to check workflow runs |
261| CI still running | gh pr checks --watch |
262| Logs pending | Retry with job logs API |
263| No failed checks | All passing ✅ |
264| Rate limited | Wait and retry |
265| Flaky test | Re-run: gh run rerun {RUN_ID} --failed |
266
In the file
SKILL.md1,154 words
Files1
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,065
on trigger
The instruction body, read only when the skill fires.
1.1%
of a 200k window
Ten skills this size would take about 11% of the window before you open a file.
050k100k150k200k context window

2.1k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 8.5 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md8.5 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$12 once
Fix CI Failures · Apache-2.0 · streamlit
one-time
Price$12 once
LicenceApache-2.0 — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are Apache-2.0, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$12
Referencestreamlit/fix-ci-failures

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0