ios-build-and-test
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.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
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.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "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.
التدقيق الأمني
آمن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.
عوامل الخطر
⚙️ الأوامر الخارجية (26)
📁 الوصول إلى نظام الملفات (2)
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/macswarm-ios-build-and-test/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](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
سبب هذا التقييم موثوقية الأدلة: متوسطما الذي يمكنك بناؤه
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 this Mac for Xcode and available iOS Simulator runtimes. Report missing prerequisites without installing anything.
Find this repository's workspace and app schemes. Ask me about ambiguous schemes, then build the selected scheme on an available Simulator.
Run tests affected by my changes, then the full suite. Launch the app and capture each changed screen. Report failures and verification gaps.
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.