==> Tapping skiptools/skip Cloning into '/opt/homebrew/Library/Taps/skiptools/homebrew-skip'... Tapped 1 cask (15 files, 417KB).

% brew install skip

==> Downloading https://source.skip.dev/skip/releases/download/1.0.0/skip.zip ==> Installing dependencies: android-platform-tools ==> Downloading https://dl.google.com/android/repository/platform-tools_r34.0.5-darwin.zip ==> Installing Cask android-platform-tools ==> Linking Binary 'adb' to '/opt/homebrew/bin/adb' 🍺 android-platform-tools was successfully installed! ==> Installing Cask skip ==> Linking Binary 'skip' to '/opt/homebrew/bin/skip'

▄▄▄▄▄▄▄ ▄▄▄ ▄▄▄ ▄▄ ▄▄▄▄▄▄▄ █ ██ █ █ ██ ██ █ █ ▄▄▄▄▄██ █▄█ ██ ██ ▄ █ █ █▄▄▄▄▄██ ▄██ ██ █▄█ █ █▄▄▄▄▄ ██ █▄██ ██ ▄▄▄█ ▄▄▄▄▄█ ██ ▄ ██ ██ █ █▄▄▄▄▄▄▄██▄▄▄█ █▄██▄▄██▄▄▄█

Welcome to Skip 1.7.0!

Run "skip checkup" to perform a full system evaluation. Run "skip create" to start a new project.

Visit https://skip.dev for documentation, samples, and FAQs.

Happy Skipping!

🍺 skip was successfully installed!

This will download and install the skip tool itself, as well as the gradle and Android SDK dependencies that are necessary for building and testing the Kotlin/Android side of your apps.

> [!NOTE]
> The skip tool installed via Homebrew is the exact same binary that is used by the Skip Xcode plugin, but they are installed in separate locations and updated through different mechanisms (the Homebrew Cask for the CLI and the skip/Package.swift for the SwiftPM plugin).

> [!CAUTION]
> Linux and Windows support is preliminary and currently doesn't support many features, but it can be used for creating, building, testing, and exporting framework projects as well as running the skip android frontend for the Swift SDK for Android. For creating and building full app projects, macOS is required.

Skip Commands
skip upgrade: Upgrade to the latest Skip version

skip checkup: Run tests to ensure Skip is in working order

skip create: Create a new Skip project interactively

skip init: Initialize a new Skip project

skip doctor: Evaluate and diagnose Skip development environment

skip verify: Verify Skip project

skip export: Export the Gradle project and built artifacts

skip test: Run parity tests and generate reports

skip icon: Create and manage app icons

skip devices: List connected devices and emulators/simulators

skip android: Perform a native Android package command

skip android build: Build the native project for Android

skip android test: Test the native project on an Android device or emulator

skip android emulator create: Install and create an Android emulator image

skip android emulator list: List installed Android emulators

skip android emulator launch: Launch an Android emulator

skip android sdk list: List the installed Swift Android SDKs

Local Skip Development
Run ./scripts/skip to build and run the Skip CLI tool from source. (It runs swift run SkipRunner, passing in a $SKIP_COMMAND_OVERRIDE environment variable.)

In order to iterate on local changes to the skipstone binary that the Skip plugin uses,
create an Xcode workspace that includes a local checkout of 
skipstone.git
and
skip.git
(or forks of those repositories),
along with any Skip apps or frameworks where you want to test the changes.

The key is that the _current working directory for Xcode must be the skipstone folder_.
This is the magic property that tells the Skip plugin to use the locally-built skip binary
rather than the remote binary that is referenced by the plugins specification in Package.skip.

In order to open Xcode from the skipstone folder, it must be done from the Terminal,
like so:

If you are successfully using the local Skip build for your plugin, this will be 
indicated in the Xcode Build log in the Report Navigator tab. E.g., when launching a Skip app,
expanding the Run skip gradle messages will reference the _local_ build of skip,
like so:

For framework projects (e.g., when building or running tests), the indication that it is
using the local build will come from the plugin log message for the target. The indication
that it is a local debug build will be that there is an asterisk ("*") after the
Skip version number at the beginning of the skipstone plugin output, like so:

[!CAUTION]

Releasing Skip

• https://github.com/skiptools/skipstone.git
• https://github.com/skiptools/skip.git
• https://github.com/skiptools/homebrew-skip.git

[!NOTE]

You must have write and release permissions for each of these repositories in order to be able to create a release.

[!TIP]

The release script will do the following:

Contributing

It is wise to discuss any major intended changes on the discussions board before embarking on any big projects.

License