agentleFS
Sign inStart free
kaeawckaeawc/auto-mobile/skills/ios-swift-ci/SKILL.md

ios-swift-ci

Skill56 starsChanged 36 days agoApache-2.0View on GitHub

Use this workflow skill to triage an AutoMobile iOS or Swift CI failure from the exact job evidence, distinguish required checks from advisory simulator failures, and run the fast local Swift validation.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use this for SwiftLint, Swift Code Coverage, iOS Build, Swift package, WHEP, or XCTestRunner Simulator Tests failures.

    line 8
  2. Very specific:

    Read the failed job by run and job ID with gh run view <run-id> --job <job-id> --log-failed.

    line 16
  3. Distinctive:

    Before merge, refresh the exact head on latest main.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

iOS/Swift CI Triage

Use this for SwiftLint, Swift Code Coverage, iOS Build, Swift package, WHEP, or XCTestRunner Simulator Tests failures.

  1. Resolve the exact PR head and current main base. Do not trust a prior green head after a rebase or merge queue update.
  2. Identify whether the check is required. XCTestRunner Simulator Tests is advisory (nightly, or on a PR labelled run-ios-sim); the required iOS checks are SwiftLint, Swift Code Coverage, and iOS Build.
  3. Read the failed job by run and job ID with gh run view <run-id> --job <job-id> --log-failed. If it is incomplete, retrieve the job log or failure artifact before assigning a cause.
  4. Classify the failure as PR-caused (with a local command), PR-caused without a local command, stale-base/main-red, runner infrastructure, test flake, or advisory roll-up fan-out. Do not retry merely because a simulator job is red.
  5. For simulator jobs, preserve ownership: one explicit simulator UDID per job, used serially. Never share a simulator between parallel jobs/runners.
  6. Recognize this week's known simulator signatures: five-minute CtrlProxy UI test timeout; CtrlProxy surviving forced teardown; video recording simctl list state timeout; hierarchy UI test over 90 seconds. Gather new evidence before treating any of them as the same bug.
  7. For a Swift change, run scripts/prepush-ios.sh. It checks the pinned SwiftFormat 0.54.6, SwiftLint's error rules, swift build in XCTestRunner, and only simulator-free XCTestRunner tests.
  8. Before merge, refresh the exact head on latest main; a stale base can hide a main-red period.

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