agentskills.codes
CI

ci-failure-triage

by meshtasticCodingSource

Provides a systematic workflow to diagnose and fix build or CI failures.

CI/CDDebugging

Install

mkdir -p .claude/skills/ci-failure-triage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10504" && unzip -o skill.zip -d .claude/skills/ci-failure-triage && rm skill.zip

Installs to .claude/skills/ci-failure-triage

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when local or CI checks fail to quickly classify root cause and apply a minimal safe fix.
93 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • →Classify failures
  • →Apply minimal fixes
  • →Revalidate scopes
  • →Summarize root causes

How it works

Categorizes build failures and guides the user through targeted reruns and small, safe patches.

Inputs & outputs

You give it
CI failure logs
You get back
Restored build health

When to use ci-failure-triage

  • →Fix build failure
  • →Triage CI error
  • →Debug gradle issue

About this skill

CI Failure Triage

Use this skill when local or CI checks fail.

Goals

  • Find root cause quickly.
  • Apply minimal safe fix.
  • Revalidate only necessary scopes first.

Required Context

  • AGENTS.md
  • CONTRIBUTING.md
  • docs/ci-cd.md
  • docs/versioning.md

Triage Buckets

  • Build setup or dependency issues.
  • Lint or formatting failures.
  • Architecture rule failures (detekt ForbiddenImport + :core:verifyModuleBoundary).
  • API compatibility failures (checkKotlinAbi/updateKotlinAbi mismatch).
  • Unit or integration regressions.
  • Environment issues (JDK 21, Android SDK 35, Xcode, submodules).

Workflow

  1. Capture first failing task and first meaningful stack trace.
  2. Classify into a triage bucket.
  3. Propose smallest fix.
  4. Re-run targeted task.
  5. If green, expand to broader verification.
  6. Summarize root cause and confidence level.

Validation Commands

  • ./gradlew <failingTask>
  • ./gradlew detekt ktlintCheck
  • ./gradlew checkKotlinAbi
  • ./gradlew check

Deliverable

Provide:

  • root cause
  • exact fix
  • targeted reruns performed
  • final status and remaining risk

When not to use it

  • →When the failure is not CI-related
  • →When the fix requires major refactoring

Prerequisites

gradlew

Limitations

  • →Requires understanding of the project's CI/CD pipeline
  • →Fixes must be minimal and safe

How it compares

Provides a structured triage workflow rather than ad-hoc debugging.

Compared to similar skills

ci-failure-triage side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ci-failure-triage (this skill)03moNo flagsIntermediate
gh-fix-ci126moReviewIntermediate
fix-ci16moReviewIntermediate
analyze-failures16moCautionIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by meshtastic

View all by meshtastic →

update-design-audits

meshtastic

Use this skill when asked to update the cross-platform design audit documents in `standards/audits/` with recent pull request activity from the `meshtastic/Meshtastic-Apple` and/or `meshtastic/Meshtastic-Android` repositories. Typical triggers:

00

mqtt-kmp

meshtastic

MQTTastic Client KMP — Kotlin Multiplatform MQTT 5.0 client library project knowledge

00

pr

meshtastic

Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per .github/copilot-pull-request-instructions.md (WHY-first, categorized changes), screenshots embedded via commit-pinned raw URLs. Use whenever work is ready to go up as a PR.

00

You might also like

gh-fix-ci

openai

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.

1234

fix-ci

llama-farm

Fetch GitHub CI failure information, analyze root causes, reproduce locally, and propose a fix plan. Use `/fix-ci` for current branch or `/fix-ci <run-id>` for a specific run.

111

analyze-failures

saleor

Analyze Playwright E2E test failure reports from CI. Parses merged blob reports, groups similar errors, and delegates to specialized subagents for investigation and fixes. Use when CI tests fail or when asked to fix E2E test failures.

19

gradle-expert

vitorpamplona

Build optimization, dependency resolution, and multi-module KMP troubleshooting for AmethystMultiplatform. Use when working with: (1) Gradle build files (build.gradle.kts, settings.gradle), (2) Version catalog (libs.versions.toml), (3) Build errors and dependency conflicts, (4) Module dependencies and source sets, (5) Desktop packaging (DMG/MSI/DEB), (6) Build performance optimization, (7) Proguard/R8 configuration, (8) Common KMP + Android Gradle issues (Compose conflicts, secp256k1 JNI variants, source set problems).

19

debugging-workflows

githubnext

Guide for debugging GitHub Agentic Workflows - analyzing logs, auditing runs, and troubleshooting issues

16

fix-sync

ClickHouse

Fix the "CH Inc sync" job in a pull request by resolving conflicts in the corresponding clickhouse-private sync PR.

16

Search skills

Search the agent skills registry