/macos-runtime-debug
Create or update the project-local macOS `build_and_run.sh` script, wire the host run action when supported, then use that script as the default build/run entrypoint.
$ npx -y skills add Xopoko/plug-n-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/macos-runtime-debug
Context preview
What this command does when you run it.
Create or update the project-local macOS `build_and_run.sh` script, wire the host run action when supported, then use that script as the default build/run entrypoint.
Command definition
macos-runtime-debug.md/macos-runtime-debug
Create or update the project-local macOS `build_and_run.sh` script, wire the host run action when supported, 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`, `macos-telemetry-probe`, 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 and the host tool needs git-backed workspace features, run `git init` at the project root. 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 `../skills/macos-runtime-debugger/references/run-button-bootstrap.md` for the exact script shape and optional Codex run-action format. 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.
- Do not leave stale `Run` actions pointing at old script paths.
- Keep the no-flag script path simple: kill, build, run.
- Use `--debug`, `--logs`, `--telemetry`, or `--verify` only when the user asks for those modes.
Read more
/macos-runtime-debug
Create or update the project-local macOS `build_and_run.sh` script, wire the host run action when supported, 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`, `macos-telemetry-probe`, 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 and the host tool needs git-backed workspace features, run `git init` at the project root. 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 `../skills/macos-runtime-debugger/references/run-button-bootstrap.md` for the exact script shape and optional Codex run-action format. 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.
- Do not leave stale `Run` actions pointing at old script paths.
- Keep the no-flag script path simple: kill, build, run.
- Use `--debug`, `--logs`, `--telemetry`, or `--verify` only when the user asks for those modes.
Ready-to-install skills and plugins that make coding agents better at real development work. Plug'n Skills is a library of plugin packs for Codex, Claude Code, Cursor, and other coding agents.
Repo: Xopoko/plug-n-skills