技能 ios-build-and-test
📦

ios-build-and-test

內容修訂 r1 安全 ⚙️ 外部命令📁 檔案系統存取

Build and Verify iOS Apps in Simulator

A successful iOS build does not prove tests pass or screens display correctly. This skill guides Simulator testing, visual checks, and evidence collection for review.

支援: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 77 銅級

使用我的智慧代理安裝

將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。

智能體請求
Review the Skillstore skill "ios-build-and-test" from https://skillstore.io/skills/macswarm-ios-build-and-test.md and its manifest at https://skillstore.io/api/skills/macswarm-ios-build-and-test/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。

測試它

正在使用「ios-build-and-test」。 Illustrative request: summarize verification after building, testing, and checking the updated screen.

預期結果:

  • Environment: selected app scheme, Simulator model, iOS runtime, and Xcode version recorded.
  • Build: passed. Tests: 12 passed, zero failed.
  • Visual check: updated screen inspected; screenshot available in .build/screens/01-launch.png.
  • Not verified: physical-device behavior.

正在使用「ios-build-and-test」。 Illustrative request: report what prevents verification when Xcode is unavailable.

預期結果:

  • Verification stopped because xcodebuild is unavailable.
  • No build, tests, app launch, or screenshots were completed.
  • Xcode was not installed or modified.

安全審計

安全
v1 • 2026/10/26 開啟版本化報告

All 29 static findings are false positives involving Markdown formatting, routine local development commands, or standard output redirection. No evidence found of prompt injection, credential theft, or data exfiltration in SKILL.md. The workflow intentionally builds repository code and modifies Simulator app state, so users should use trusted projects and appropriate test devices.

1
已掃描檔案
94
分析行數
0
複核項目
0
已忽略的誤報
最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。
審計單位: codex
分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。

開啟版本化報告
安全評估

複製報告連結

https://skillstore.io/skills/macswarm-ios-build-and-test/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/macswarm-ios-build-and-test/security.svg)](https://skillstore.io/skills/macswarm-ios-build-and-test?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/macswarm-ios-build-and-test?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/macswarm-ios-build-and-test/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/macswarm-ios-build-and-test.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
學術引用 (APA · BibTeX · CFF)

APA 引用

macswarm. (2026). ios-build-and-test security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/macswarm-ios-build-and-test/audits/1

BibTeX 引用

@techreport{macswarm-macswarm-ios-build-and-test-2026, author = {macswarm}, title = {ios-build-and-test security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/macswarm-ios-build-and-test/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: "ios-build-and-test security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "macswarm" date-released: "2026-10-26" url: "https://skillstore.io/skills/macswarm-ios-build-and-test/audits/1" identifiers: - type: other value: "skillstore:macswarm-ios-build-and-test:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據 證據置信度: 中
55
架構
85
可維護性
87
內容
65
社群
83
規範符合度

你可以打造什麼

Verify an iOS feature change

Build an updated app, test affected behavior, and capture changed screens before opening a pull request.

Investigate a Simulator failure

Reproduce a failing test or app crash and collect assertion messages, process logs, and screenshots.

Review verification evidence

Collect the exact scheme, toolchain, Simulator details, test totals, and visual evidence needed to assess a proposed change.

試試這些提示

Check the development environment
Check this Mac for Xcode and available iOS Simulator runtimes. Report missing prerequisites without installing anything.
Build a selected app
Find this repository's workspace and app schemes. Ask me about ambiguous schemes, then build the selected scheme on an available Simulator.
Test and inspect changed screens
Run tests affected by my changes, then the full suite. Launch the app and capture each changed screen. Report failures and verification gaps.
Investigate a crash and prepare review evidence
Reproduce the reported crash on a selected Simulator. Collect process logs and screenshots, run relevant tests, and prepare review evidence. Avoid erasing shared devices.

最佳實務

  • Use trusted repositories and confirm the scheme and Simulator UDID before building or changing app state.
  • Preserve xcodebuild failure status when piping logs, and inspect current test results rather than inferring success from output alone.
  • Run affected tests before the full suite, inspect changed screens, and exclude generated .build artifacts from commits.

避免

  • Treating a successful build as proof that tests pass or screens look correct.
  • Guessing an ambiguous scheme or choosing a Simulator only by its display name.
  • Erasing a shared Simulator or launching duplicate builds of the same scheme.

常見問題

Does this skill install Xcode?
No. It stops and reports the missing prerequisite when xcodebuild is unavailable.
Can I use a hosted Mac?
Yes. The workflow supports local and hosted Macs with Xcode installed, including Macswarm Pods.
Is XcodeBuildMCP required?
No. Shell commands are provided. A connected XcodeBuildMCP server can supply equivalent build, test, launch, and screenshot tools.
How does it choose a scheme and Simulator?
It consults repository guidance, asks about ambiguous app schemes, and selects a Simulator by UDID, preferably one already booted.
Where are test results and screenshots stored?
Examples store test results in .build/Results.xcresult and screenshots in .build/screens. Generated .build content should not be committed.
Does a passing test suite prove the interface is correct?
No. The workflow also requires screenshots and visual inspection of changed screens, with any remaining verification gaps stated explicitly.

開發者詳細資訊

作者

macswarm

授權

MIT

Skillstore 修訂

r1

版本提示

作者未聲明版本。

引用

421fa839079609a854f1768cc54b2f311080d484

維護新鮮度

2026/10/26

使用量

0 次下載 · 0 次瀏覽

檔案結構

📄 SKILL.md

查看全部