Skills diagnose-ci-failures

📦

diagnose-ci-failures

Name: diagnose-ci-failures
Author: warpdotdev

Content revision r1 Safe ⚙️ External commands

Diagnose CI Failures Faster

CI failures can hide the first useful error among checks, logs, and repeated noise. This skill gathers relevant GitHub evidence and produces a prioritized plan for repair.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "diagnose-ci-failures" from https://skillstore.io/skills/warpdotdev-diagnose-ci-failures.md and its manifest at https://skillstore.io/api/skills/warpdotdev-diagnose-ci-failures/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/warpdotdev-diagnose-ci-failures.md Signed manifest GET /api/skills/warpdotdev-diagnose-ci-failures/manifest Signed lockfile GET /api/skills/warpdotdev-diagnose-ci-failures/lockfile

Test it

Using "diagnose-ci-failures". Diagnose the failures on pull request 42.

Expected outcome:

The Linux test job fails first because a fixture is missing. Formatting and downstream build checks may be secondary failures. Recommended order: restore the fixture, rerun tests, then address formatting.

Using "diagnose-ci-failures". Compare the failed macOS and Linux checks.

Expected outcome:

Both platforms report the same dependency resolution error.
The Windows job passed, so the issue may depend on runner configuration or lockfile handling.
Verify the dependency cache and lockfile before changing application code.

Security Audit

Safe

v1 • 9/18/2026 Open versioned report

All 25 static detections are false positives: the reported backticks occur in Markdown examples, inline code formatting, or command references. The available evidence shows no executed command, injected input, data exfiltration, or prompt-injection content.

Files scanned

114

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: claude

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/warpdotdev-diagnose-ci-failures/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/warpdotdev-diagnose-ci-failures/security.svg)](https://skillstore.io/skills/warpdotdev-diagnose-ci-failures?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/warpdotdev-diagnose-ci-failures?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-diagnose-ci-failures/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/warpdotdev-diagnose-ci-failures.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

warpdotdev. (2026). diagnose-ci-failures security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-diagnose-ci-failures/audits/1

BibTeX citation

@techreport{warpdotdev-warpdotdev-diagnose-ci-failures-2026,
  author = {warpdotdev},
  title = {diagnose-ci-failures security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/warpdotdev-diagnose-ci-failures/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "diagnose-ci-failures security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "warpdotdev"
date-released: "2026-09-18"
url: "https://skillstore.io/skills/warpdotdev-diagnose-ci-failures/audits/1"
identifiers:
  - type: other
    value: "skillstore:warpdotdev-diagnose-ci-failures:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Triage a pull request

Review failing checks on an active pull request and isolate the earliest actionable error.

Prepare a repair handoff

Convert noisy CI output into a prioritized plan that another engineer can implement.

Investigate cross-platform failures

Compare platform-specific checks and identify whether formatting, tests, builds, or tooling cause the failure.

Try These Prompts

Check my pull request

Inspect the CI status for pull request <number> in <owner>/<repo>. Summarize failed checks and the first useful error for each.

Explain the failing logs

For pull request <number>, retrieve the relevant failed job logs, remove repeated noise, and explain the likely cause in plain language.

Build a fix plan

Analyze all failed checks for pull request <number>. Group related failures, rank them by likely root cause, and create a step-by-step repair plan with verification commands.

Compare platform failures

Investigate pull request <number> across macOS, Linux, and Windows checks. Distinguish shared root causes from platform-specific issues and cite the evidence for each conclusion.

Best Practices

Provide the repository and pull request number so the diagnosis targets the correct checks.
Fix the earliest root-cause failure before addressing downstream or repeated errors.
Review the proposed commands and changes before running them in a repository.

Avoid

Do not treat every failed check as an independent root cause.
Do not expose private logs or credentials in copied prompts or issue comments.
Do not rerun expensive workflows repeatedly without changing the suspected cause.

Frequently Asked Questions

What does this skill inspect?

It inspects pull request checks, failed workflow jobs, and accessible GitHub Actions logs.

Does it fix the code?

No. It explains the evidence and prepares a repair plan for an engineer to review and implement.

What access is required?

The GitHub CLI must be authenticated and authorized to read the repository and relevant workflow logs.

Can it diagnose local test failures?

It focuses on CI evidence. You can provide local output separately, but local execution is not its primary capability.

How does it handle many failures?

It groups related checks and prioritizes likely root causes before secondary failures.

Should I run suggested commands immediately?

No. Review each command, its scope, and its repository impact before execution.

Developer Details

Author

warpdotdev

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/warpdotdev/common-skills/tree/69b4753651ab7fab518c82be087b9f1d5b966631/.agents/skills/diagnose-ci-failures

Ref

6e663c781098ffdba3ad66055d217e0dd327bd20

Maintenance freshness

9/18/2026

Usage

0 downloads · 0 views

File structure

📄 SKILL.md