---
name: local-validation-swift
description: "Use before running local validation in this Swift repository: `xcodebuild test`, simulator destinations, `swift-format`, derived data in a worktree, or result bundles. Covers how CI picks a simulator, which CI runs test and which only lint, project and dependency setup, the fixed `-derivedDataPath` rule, what Release Please does and does not version, and the formatter rules."
title: local-validation-swift
canonical_url: https://skilld.dev/gh/bydradev/gh-repo-bootstrapper/local-validation-swift
last_updated: 2026-10-30T03:16:22.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install bydradev/gh-repo-bootstrapper/local-validation-swift`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/local-validation-swift`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/bydradev/gh-repo-bootstrapper/local-validation-swift) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/local-validation-swift`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/local-validation-swift --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/local-validation-swift --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Local validation for Swift

If `## Project specifics` in `AGENTS.md` names a repository-owned validation
skill, load it first; where it is narrower, it governs.

The commands to run before pushing are in the `## Tooling` section of `AGENTS.md`. This skill covers the detail behind them.

## Simulator destinations

As generated, `.github/workflows/test.yml` runs on `macos-26`. For
`iphone`/`ipad` destinations it resolves an available simulator's UDID at run
time (via `xcrun simctl`) and passes
`-destination "platform=iOS Simulator,id=<udid>"`: a UDID rather than a
`name=` destination, since simulator names aren't unique across installed
runtimes.

## CI validation tiers

As generated, CI validates in two tiers. This repository owns
`.github/workflows/ci.yml` and `test.yml`, so check them, and the `full` input
that the template-owned `release-please.yml` passes to `test.yml`, for its
current tiers:

- **Pull requests (`ci.yml`) and ordinary pushes to `main`:** run only
  `xcrun swift-format lint --recursive --strict .`. `xcodebuild test` is
  skipped, so a green pull request does not mean the tests passed; run them
  locally first.
- **Release Please merge (`chore(main): release`) and a manual dispatch of
  `release-please.yml`:** run the formatter and `xcodebuild test`. A release
  is tagged only after this passes.

## Dependencies

# <<XCODEGEN_DEPENDENCY_NOTE>>

## Worktrees

In a worktree, pass one fixed `-derivedDataPath` for that worktree, reuse it
across runs, and delete it when the worktree is removed. Never choose a new
derived-data path per run or per commit. Keep it outside the source tree (for
example next to the worktree), because `swift-format --recursive .` and search
tools would otherwise scan it. Write `-resultBundlePath` bundles to the
session's scratch directory and delete them once read.

## Versioning

As generated, `release-please-config.json` uses the `simple` release type:
Release Please maintains the changelog, tag, and GitHub release, but does not
change the app's `MARKETING_VERSION` or `CURRENT_PROJECT_VERSION`, wherever
they are set. For `MARKETING_VERSION`, update it deliberately for a build you
ship, or point `extra-files` in that file at the field that holds it.
`extra-files` only replaces a semantic version, so `CURRENT_PROJECT_VERSION`
needs its own, separately verified build-number step.

## Formatting

As generated, CI lints with `xcrun swift-format lint --recursive --strict .`,
so a violation fails the build. Never suppress or manually circumvent a
formatter diagnostic (no per-line `// swift-format-ignore`, no hand-editing
around a rule). Rule configuration lives in `.swift-format` at the repo root;
if a rule is wrong for this codebase, change that file deliberately and say why
in the commit or PR. It is the only sanctioned escape hatch.

## Sources

- `-derivedDataPath` and `-resultBundlePath`: `xcodebuild -help` in Xcode
  27.0, checked 2026-09-29.
- What the `simple` release type versions, and `extra-files`: release-please
  v17.11.2's `simple` strategy, generic updater, and config schema, checked
  2026-09-29.
