agentleFS
Sign inStart free
kaeawckaeawc/auto-mobile/skills/ci-failure-triage/SKILL.md

ci-failure-triage

Skill56 starsChanged 35 days agoApache-2.0View on GitHub

Classify failed pull-request workflow runs, distinguish required from advisory jobs, and avoid re-fixing documented non-fixes.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dependency-cve-sweep, fleet-standard-adoption and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • berntpoppSkill

    dependency-cve-sweep

    Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.

    Also in 12 projects that use this

  • berntpoppSkill

    fleet-standard-adoption

    Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.

    Also in 12 projects that use this

  • VersoXBTSkill

    code-quality-review

    Perform structured code reviews enforcing quality standards, naming conventions, architecture patterns, and team agreements. Use when the user says 'review this code', 'code review', 'check quality', 'review my PR', 'what's wrong with this', 'improve this code', 'review before merge', 'peer review', or 'audit this'. Also triggers on 'code quality', 'review standards', 'enforce conventions', 'tech debt check', 'lint review', or when user completes a significant code change.

    Also in 12 projects that use this

  • Microsoft AzureSkill

    release-readiness

    Complete ODIN release documentation and validation checks before declaring user-visible work complete, preparing a release, or opening the Release-to-main pull request.

    Also in 14 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 13 projects that use this

  • +2 more from berntpopp

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this for a failed pull_request.yml run or a red roll-up gate.

    line 8
  2. Very specific:

    Run bash scripts/ci/classify-failure.sh <run-id> first.

    line 11
  3. Very specific:

    When the verdict is INVESTIGATE with a named test file:line or missing import path, act on that diagnosis.

    line 30
  4. Very specific:

    Do not re-fix KNOWN-NONFIX signatures.

    line 33
  5. Very specific:

    Use check-ci when the failure needs full exact-head PR-state and log analysis.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CI Failure Triage

Use this for a failed pull_request.yml run or a red roll-up gate. It is read-only unless the user also asks to fix a confirmed cause.

  1. Run bash scripts/ci/classify-failure.sh <run-id> first. It lists each failed/cancelled job, failed step, check-run annotations, and a matching scripts/ci/known-flakes.txt verdict.
  2. The green-main ruleset requires 22 status checks; it is the authoritative list (gh api repos/kaeawc/auto-mobile/rulesets, then rulesets/<id> and its required_status_checks rule). The roll-up gates (IDE Plugin, iOS Build, Shell Tests) only give a required context a stable name over matrix or conditionally skipped jobs; the other required checks are ordinary jobs that report directly, so read the failing job itself. Advisory means not in the ruleset (simulator, emulator, device-capture lanes): it never blocks a merge. The Linux unit run and its 100 ms budget step live in the required Node TypeScript Build and Test (ubuntu-latest) job (#10893), so a budget breach there blocks; classify it before rerunning (a loaded-runner overage is RERUN-DONT-FIX). Runs from before the non-required iOS, Android, Node Tests, and WebRTC roll-ups were removed still classify those contexts as CHECK-UPSTREAM-FIRST when only an advisory lane failed.
  3. For CHECK-UPSTREAM-FIRST, inspect the named upstream row before retrying or filing work. A red aggregator is not a test diagnosis.
  4. When the verdict is INVESTIGATE with a named test file:line or missing import path, act on that diagnosis. Treat a shard as signal-killed only when the output says killed by signal.
  5. Do not re-fix KNOWN-NONFIX signatures. In particular, a Dependabot sharp/jimp bump that breaks the pinned clean-room graph is designed to be rejected; close or ignore that Dependabot PR instead of changing runtime dependencies.
  6. For integration-test or runtime-graph input changes, run bash scripts/prepush-integration.sh before pushing. It runs only changed integration files and only runs the clean-room runtime audit when its inputs changed.

Use check-ci when the failure needs full exact-head PR-state and log analysis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free