agf-running-apple-sit
App Genesis Forge equips Claude Code with a structured development pipeline featuring 19 specialized roles working in concert. This skill automates simulator-based integration testing, catching composition issues before they reach code review—ensuring quality gates function like a lean manufacturing line rather than relying on a single agent.
agf-running-apple-sit automates simulator-based SIT by executing xcodebuild test across iOS and macOS targets before code review. The skill verifies component composition and SwiftUI-AppCore-client-backend integration using mock backends, capturing xcresult evidence for audit trails. Run xcodebuild test with your universal target to test both platforms simultaneously, then document results in progress/apple-dev.md for the code reviewer.
AI-generated summary based on this skill's SKILL.md
Install
pcliangx/AppGenesisForge/agf-running-apple-sit · repository language: Python
git clone https://github.com/pcliangx/AppGenesisForge
cp -r AppGenesisForge/.claude/skills/agf-running-apple-sit ~/.claude/skills/agf-running-apple-sitFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I run Apple integration tests with xcodebuild on simulator?
agf-running-apple-sit automates simulator-based SIT by executing xcodebuild test across iOS and macOS targets before code review. The skill verifies component composition and SwiftUI-AppCore-client-backend integration using mock backends, capturing xcresult evidence for audit trails. Run xcodebuild test with your universal target to test both platforms simultaneously, then document results in progress/apple-dev.md for the code reviewer.
What's the scope of agf-running-apple-sit versus unit tests and E2E?
agf-running-apple-sit focuses on system integration testing (SIT)—the middle layer between unit tests and end-to-end tests. It verifies that SwiftUI, AppCore, client, and mock backend components compose correctly without regression. Unlike unit tests (isolated functions) or E2E tests (full user flows via XCUITest), SIT validates integration points using xcodebuild test on the simulator before handoff to product lead and code review.
How does agf-running-apple-sit document SIT evidence for code reviewer audit?
agf-running-apple-sit captures xcodebuild test results and acceptance criteria (AC) verdicts, storing them in progress/apple-dev.md as a structured evidence sink. This markdown log tracks SIT progress, defect findings, and test outcomes so code reviewers can audit quality gates without re-running tests. Each entry links xcresult artifacts and AC pass/fail status for transparent handoff.
What pre-conditions must pass before agf-running-apple-sit runs on a feature branch?
agf-running-apple-sit assumes unit tests pass on your feature branch first. The skill then layers SIT atop that foundation, using mock backend APIs (FastAPI localhost or OpenAPI-generated stubs) to verify integration without external dependencies. Ensure your universal target builds for both iOS and macOS, simulator devices are available via xcrun simctl, and AppCore-client composition is stable before SIT execution.
How does agf-running-apple-sit prevent anti-patterns in universal target testing?
agf-running-apple-sit enforces discipline by running xcodebuild test against universal targets on both iOS and macOS simulators in a single pass, avoiding platform-specific test skips or incomplete coverage. The skill documents which platforms were tested in xcresult and progress/apple-dev.md, ensuring no platform falls through the cracks. Mock backend discipline (APIProtocol stubs) keeps tests deterministic across platforms.
When should I hand off agf-running-apple-sit results to the product lead?
agf-running-apple-sit hands off SIT results to the product lead after xcodebuild test completes, AC verdicts are recorded in progress/apple-dev.md, and no regressions in SwiftUI-AppCore-client-backend integration are detected. This occurs before code review, allowing product lead to validate feature scope while code reviewer audits SIT evidence. If defects emerge, distinguish SIT failures from unit test issues to guide remediation.
SKILL.md
rendered from the published skill — quoted content, verbatim
Running Apple SIT (xcodebuild + simulator)
Use this skill when:
- apple-dev finished feature code + Unit tests and is about to enter code-review
- apple-dev needs to verify a fix doesn't regress integration（视图 ↔ AppCore ↔ 生成 client ↔ 后端契约）
What Apple SIT is — and is not
SIT verifies that independently-developed components compose correctly at the app-integration layer — SwiftUI 视图 ↔ AppCore 业务层 ↔ swift-openapi-generator 生成的 client ↔（mock 后端）。It is NOT:
- Unit tests（Swift Testing，
swift test已在分支全绿） - E2E（XCUITest 对签名分发包——apple-qa-engineer 在发布构建后跑）
- UAT（业务签字，product-lead 驱动）
If a failure reproduces in plain swift test with mocks, it's a unit-level miss — fold it back into the unit suite, don't write it up as a SIT defect.
Pre-conditions
- [ ] Feature
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/agf-running-apple-sit/SKILL.md