Index of every page on this site: llms.txt
All skills
bydradev avatar

/local-validation-swift

@20b39bd
Run it yourself

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.

  • 1 file
  • 3.5 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/bydradev/gh-repo-bootstrapper/local-validation-swift

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈100 tokens for metadata: the name and description. ≈776 when used: this file.

Description uses 5.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈402 characters, or 5.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 20b39bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month

README badge

README badge for bydradev/gh-repo-bootstrapper/local-validation-swift