CtrlK
BlogDocsLog inGet started
Tessl Logo

build-and-run-macos-app

Slash command that creates or updates the project-local macOS `script/build_and_run.sh` and uses it as the default build/run entrypoint. Invoke explicitly with /build-and-run-macos-app — this skill never self-triggers.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/build-and-run-macos-app/SKILL.md
SKILL.md
Quality
Evals
Security

Build And Run macOS App

Create or update the project-local macOS build_and_run.sh script, then use that script as the default build/run entrypoint.

Arguments

  • scheme: Xcode scheme name (optional)
  • workspace: path to .xcworkspace (optional)
  • project: path to .xcodeproj (optional)
  • product: SwiftPM executable product name (optional)
  • mode: run, debug, logs, telemetry, or verify (optional, default: run)
  • app_name: process/app name to stop before relaunching (optional)

Workflow

  1. Detect whether the repo uses an Xcode workspace, Xcode project, or SwiftPM package.
  2. If the workspace is not inside git yet, run git init at the project root so git-backed editor features unlock.
  3. Create or update script/build_and_run.sh so it always stops the current app, builds the macOS target, and launches the fresh result.
  4. For SwiftPM, keep raw executable launch only for true CLI tools; for AppKit/SwiftUI GUI apps, create a project-local .app bundle and launch it with /usr/bin/open -n.
  5. Support optional script flags for --debug, --logs, --telemetry, and --verify.
  6. Follow the canonical bootstrap contract in ../build-run-debug/references/build-script.md for the exact script shape.
  7. Run the script in the requested mode and summarize any build, script, or launch failure.

Guardrails

  • Do not initialize a nested git repo inside an existing parent checkout.
  • Keep the no-flag script path simple: kill, build, run.
  • Use --debug, --logs, --telemetry, or --verify only when the user asks for those modes.
Repository
robinebers/openusage
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.