Agent skill

Xcodebuild Testing

Run unit tests, UI tests, or specific test cases for VivaDicta using xcodebuild command-line tool

MITAuto-check passedTesting & QA

Install Xcodebuild Testing

skills CLI

$ npx skills add n0an/VivaDicta --skill xcodebuild-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install n0an/VivaDicta xcodebuild-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/xcodebuild-testing .claude/skills/xcodebuild-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "xcodebuild-testing" agent skill from https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing into .claude/skills/xcodebuild-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xcodebuild-testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add n0an/VivaDicta --skill xcodebuild-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install n0an/VivaDicta xcodebuild-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/xcodebuild-testing .agents/skills/xcodebuild-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "xcodebuild-testing" agent skill from https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing into .agents/skills/xcodebuild-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xcodebuild-testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add n0an/VivaDicta --skill xcodebuild-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install n0an/VivaDicta xcodebuild-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/xcodebuild-testing .cursor/skills/xcodebuild-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "xcodebuild-testing" agent skill from https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing into .cursor/skills/xcodebuild-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xcodebuild-testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/n0an/VivaDicta.git --path .agents/skills/xcodebuild-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add n0an/VivaDicta --skill xcodebuild-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install n0an/VivaDicta xcodebuild-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/xcodebuild-testing .gemini/skills/xcodebuild-testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "xcodebuild-testing" agent skill from https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing into .gemini/skills/xcodebuild-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xcodebuild-testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install n0an/VivaDicta xcodebuild-testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add n0an/VivaDicta --skill xcodebuild-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/xcodebuild-testing .github/skills/xcodebuild-testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "xcodebuild-testing" agent skill from https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing into .github/skills/xcodebuild-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xcodebuild-testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add n0an/VivaDicta --skill xcodebuild-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install n0an/VivaDicta xcodebuild-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/n0an/VivaDicta.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/xcodebuild-testing .opencode/skills/xcodebuild-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "xcodebuild-testing" agent skill from https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcodebuild-testing into .opencode/skills/xcodebuild-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xcodebuild-testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: xcodebuild-testing
GitHub stars: 126
Token cost: ~3.3k tokens
SKILL.md length: 954 words
Files: 2
Skills in repo: 20
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run unit tests, UI tests, or specific test cases for VivaDicta using xcodebuild command-line tool

Works in 3 steps: Test target name - Usually… → Test class name - The Swift class… → Test method name - The specific test…
Tasks that involve Test generation
SKILL.md covers Related Skills, Skill Flow, Path A: Run All Tests and Path B: Run Specific Test, plus 5 more sections
Calls xcodebuild, xcrun and brew

What it does

Xcodebuild Testing is an agent skill from n0an/VivaDicta. Run unit tests, UI tests, or specific test cases for VivaDicta using xcodebuild command-line tool

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA, covering Test generation and Unit testing. It works with Xcode. The repository describes itself as: iOS & watchOS speech-to-text app with AI voice keyboard, on-device RAG, and chat with your notes - powered by Apple Foundation Models, WhisperKit, NVIDIA Parakeet, and 20+ AI…. The licence is MIT.

When your agent uses it

Tasks that involve Test generation
Tasks that involve Unit testing

Example prompts

“/xcodebuild-testing”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Test target name - Usually VivaDictaTests or VivaDictaUITests
Test class name - The Swift class containing the test
Test method name - The specific test method

What it can do on your machine

Read from SKILL.md and the folder at commit b141304. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- xcodebuild
- xcrun
- brew
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Xcodebuild Testing loads about 3.3k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 954 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~29
When it runs · the whole SKILL.md, loaded when a task matches: ~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from n0an/VivaDicta at commit b141304, republished under its MIT licence (© n0an). 954 words, ~3,346 tokens.

Download SKILL.mdSave it as .claude/skills/xcodebuild-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: xcodebuild-testing
description: Run unit tests, UI tests, or specific test cases for VivaDicta using xcodebuild command-line tool

Xcodebuild Testing

Use this skill when you need to run unit tests, UI tests, or specific test cases for the VivaDicta iOS app using xcodebuild command-line tool.

See logs-start and logs-stop for capturing logs during test execution
See axe-simulator-control for automating simulator interactions during UI tests
See screenshot for capturing screenshots during test failures

Skill Flow

Example queries:
- "run all tests"
- "run tests for the app"
- "run a specific test"
- "run only failing tests"
- "run tests and show me the results"
Notes:
- Uses native xcodebuild test command (not XcodeBuildMCP)
- Output piped through xcsift (or xcbeautify) for readable formatting
- Default simulator: iPhone 17 Pro Max, OS=26.4
- Tests run in Debug configuration
- Workspace path: ./VivaDicta.xcodeproj/project.xcworkspace
- Scheme: VivaDicta

1. Determine Test Scope

Run All Tests if:

Want to run entire test suite
Verifying overall app health
Running tests in CI/CD

→ Continue with Path A: Run All Tests (step 2A)

Run Specific Test if:

Debugging a specific failing test
Testing a specific feature or component
Want faster feedback on targeted functionality

→ Continue with Path B: Run Specific Test (steps 2B-3B)

Run Test Class if:

Want to run all tests in a specific test class
Testing a specific module or feature area
Iterating on a group of related tests

→ Continue with Path C: Run Test Class (steps 2C-3C)

Run with Log Capture if:

Need detailed logs from test execution
Debugging test failures
Want to analyze app behavior during tests

→ Continue with Path D: Run with Log Capture (steps 2D-4D)

Path A: Run All Tests

2A. Run Full Test Suite

bash

# Run all tests in the VivaDicta scheme
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test 2>&1 | xcsift

# Alternative: Save test results to file
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test 2>&1 | tee test_results.txt 2>&1 | xcsift

Available parameters:

-scheme: Xcode scheme to build and test (VivaDicta)
-configuration: Build configuration (Debug or Release)
-workspace: Path to workspace file
-destination: Simulator or device to run tests on
test: The xcodebuild action to run tests

Notes:

xcsift formats the output for better readability (alternatively xcbeautify)
tee allows saving output to file while still displaying it
Simulator will be booted automatically if not already running
Tests run in parallel by default (can be disabled with -parallel-testing-enabled NO)

Path B: Run Specific Test

2B. Identify Test Target

You need three pieces of information:

Test target name - Usually VivaDictaTests or VivaDictaUITests
Test class name - The Swift class containing the test
Test method name - The specific test method

bash

# Example test identifier format:
# VivaDictaTests/TranscriptionManagerTests/testWhisperKitTranscription
# ^target         ^class                  ^method

Finding test names:

bash

# List all test classes and methods
xcodebuild -scheme VivaDicta \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -dry-run 2>&1 | grep "Test Case" 2>&1 | xcsift

# Or search in test files
find . -name "*Tests.swift" -exec grep -H "func test" {} \;

3B. Run Specific Test

bash

# Run a single test method
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -only-testing:VivaDictaTests/TranscriptionManagerTests/testWhisperKitTranscription 2>&1 | xcsift

# Run multiple specific tests
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test \
  -only-testing:VivaDictaTests/TranscriptionManagerTests/testWhisperKitTranscription \
  -only-testing:VivaDictaTests/TranscriptionManagerTests/testParakeetTranscription 2>&1 | xcsift

Parameters:

-only-testing:<Target>/<Class>/<Method> - Specifies exact test to run
Can use multiple -only-testing flags to run specific tests

Notes:

Much faster than running all tests
Useful for TDD (Test-Driven Development) workflows
Can specify target/class without method to run all tests in that class

Path C: Run Test Class

2C. Identify Test Class

bash

# Find test classes in the project
find . -name "*Tests.swift" | sed 's/.*\///' | sed 's/.swift//'

# Example output:
# TranscriptionManagerTests
# WhisperKitServiceTests
# AIServiceTests

3C. Run All Tests in Class

bash

# Run all tests in a specific test class
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -only-testing:VivaDictaTests/TranscriptionManagerTests 2>&1 | xcsift

# Run multiple test classes
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test \
  -only-testing:VivaDictaTests/TranscriptionManagerTests \
  -only-testing:VivaDictaTests/AIServiceTests 2>&1 | xcsift

Notes:

Omit the method name to run all tests in the class
Format: -only-testing:<Target>/<Class>
Useful for feature-specific test runs

Path D: Run with Log Capture

2D. Start Log Capture Session

Start log capture using the logs-start skill. With no argument it captures the simulator, which is what these tests run against.

This will:

Automatically detect the booted simulator
Start capturing VivaDicta logs in the background
Save logs to logs/sim-YYYYMMDD-HHMMSS.log
The app continues running without restart

3D. Run Tests

bash

# Run tests while logs are being captured
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test 2>&1 | xcsift

4D. Stop Log Capture and Analyze

Stop capture with the logs-stop skill.

Useful follow-up filters:

logs-stop errors
logs-stop warnings

Manual analysis remains the same:

bash

grep -i "error\\|fail\\|crash" logs/sim-*.log
grep "test" logs/sim-*.log

Common Workflows

Quick Test Run During Development

bash

# Run specific test you're working on
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -only-testing:VivaDictaTests/MyFeatureTests/testNewFeature 2>&1 | xcsift

Test Run with Results Saved

bash

# Run all tests and save results
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test 2>&1 | tee logs/test_results_$(date +%Y%m%d_%H%M%S).txt 2>&1 | xcsift

# Check exit code
echo "Test exit code: $?"

Run Tests on Different Simulator

bash

# List available simulators
xcrun simctl list devices available

# Run on specific simulator
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 15 Pro,OS=17.5' \
  test 2>&1 | xcsift

Run Only Failed Tests from Previous Run

bash

# After a test run fails, rerun only failed tests
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -only-testing:VivaDictaTests/FailedTestClass/testThatFailed 2>&1 | xcsift

Parallel Test Execution

bash

# Enable parallel testing (default)
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -parallel-testing-enabled YES 2>&1 | xcsift

# Disable parallel testing (for debugging race conditions)
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -parallel-testing-enabled NO 2>&1 | xcsift

Test Run with Code Coverage

bash

# Run tests with code coverage enabled
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -enableCodeCoverage YES 2>&1 | xcsift

# View coverage report location
# DerivedData/<project>/Logs/Test/*.xcresult

Debug Test Failures with Screenshots

bash

# 1. Run tests and note which test fails
xcodebuild -scheme VivaDicta \
  -configuration Debug \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace \
  -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max,OS=26.4' \
  test -only-testing:VivaDictaTests/UITests/testLoginFlow 2>&1 | xcsift

# 2. If test fails, capture screenshot using xcrun simctl
xcrun simctl io booted screenshot logs/test_failure_$(date +%Y%m%d_%H%M%S).png

Show full SKILL.md (412 more words)Show less

Troubleshooting

"Testing failed" with no clear error:

Check if simulator is booted: xcrun simctl list | grep Booted
Verify scheme exists: xcodebuild -list
Clean build folder: xcodebuild clean then retry
Check for compilation errors in the test target

"Unable to boot device" error:

Simulator may be stuck: xcrun simctl shutdown all then retry
Check simulator exists: xcrun simctl list devices
Free up disk space if needed
Restart Simulator.app

Tests hang or timeout:

Check for UI tests waiting for elements that don't appear
Disable parallel testing: -parallel-testing-enabled NO
Increase test timeout in scheme settings (Xcode UI)
Check for deadlocks in test code

"Test target not found" error:

Verify test target name is correct (case-sensitive)
Check test target is included in scheme: xcodebuild -list
Ensure test files are members of test target in Xcode

xcsift not found:

Install xcsift: brew install xcsift (or use xcbeautify as alternative: brew install xcbeautify)
Or run without it (remove 2>&1 | xcsift from command)

Specific test not found:

Verify test method starts with test prefix
Check test class inherits from XCTestCase
Ensure test method is func test...() not private
Try -dry-run to see all available tests

Simulator wrong OS version:

List available OS versions: xcrun simctl list runtimes
Download runtime in Xcode: Settings → Platforms
Adjust destination to match available runtime

Best Practices

Use xcsift for readable output:
- Always pipe through xcsift for formatted output (project standard)
- Install with: brew install xcsift (or xcbeautify as alternative)
Run specific tests during development:
- Faster feedback loop
- Use -only-testing for TDD workflow
- Run full suite before committing
Save test results for analysis:
- Use tee to save output while viewing it
- Store in logs/ directory (gitignored)
- Include timestamps in filenames
Combine with log capture for debugging:
- Start log capture before running tests
- Capture both test output and app logs
- Cross-reference timestamps
Use consistent simulator:
- Stick to project default: iPhone 17 Pro Max, OS=26.4
- Document in AGENTS.md if changed
- Match CI/CD simulator configuration

Clean build when tests behave unexpectedly:

bash

xcodebuild clean -scheme VivaDicta \
  -workspace ./VivaDicta.xcodeproj/project.xcworkspace

Check exit codes in scripts:

bash

xcodebuild ... test 2>&1 | xcsift
if [ $? -ne 0 ]; then
  echo "Tests failed!"
  exit 1
fi

Organize test output:

bash

mkdir -p logs/test-results
xcodebuild ... test 2>&1 | tee logs/test-results/run_$(date +%Y%m%d_%H%M%S).txt 2>&1 | xcsift

Use test plans for different configurations:
- Create test plans in Xcode for different scenarios
- Reference with -testPlan <name> flag
Monitor test execution time:
- Use -result-bundle-path to save detailed results
- Analyze .xcresult bundles for performance insights

Files

SKILL.md and 1 other file in .agents/skills/xcodebuild-testing of n0an/VivaDicta.

SKILL.md
agents/openai.yaml

Open the folder on GitHubat commit b141304

Compare with similar skills

Xcodebuild Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Xcodebuild Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Xcodebuild Testing this skilln0an/VivaDicta	126	—	~3.3k	Automated safety check: Pass	MIT	2 days ago
Adk Verify Snippetsgoogle/adk-python	22k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Hermetic Python Unit TestsdimensionalOS/dimos	4.6k	—	~1.4k	Automated safety check: Pass	Custom licence	today
OpenROAD Module Test AdderThe-OpenROAD-Project/OpenROAD	3.2k	—	~1.8k	Automated safety check: Pass	BSD-3-Clause	yesterday
Concept Page Test Writerleonardomso/33-js-concepts	67k	—	~5.5k	Automated safety check: Pass	MIT	27 days ago
ScottPlot Test RunnerScottPlot/ScottPlot	6.8k	—	~308	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Adk Verify Snippets
google/adk-python
Official
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…
22k GitHub stars~1.4k tokensUpdated today
Testing & QAAuto-check passed
Hermetic Python Unit Tests
dimensionalOS/dimos
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.
4.6k GitHub stars~1.4k tokensUpdated today
Testing & QAAuto-check passed
OpenROAD Module Test Adder
The-OpenROAD-Project/OpenROAD
Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.
3.2k GitHub stars~1.8k tokensUpdated yesterday
Testing & QAAuto-check passed
Concept Page Test Writer
leonardomso/33-js-concepts
Generates Vitest tests for every runnable code example on a JavaScript concept documentation page, following a four-phase extraction and conversion process.
67k GitHub stars~5.5k tokensUpdated 27 days ago
Testing & QAAuto-check passed
ScottPlot Test Runner
ScottPlot/ScottPlot
Run or add ScottPlot 5 tests. Use for unit-test and cookbook-test work; unless explicitly asked otherwise, restrict manual test execution to the Unit Tests…
6.8k GitHub stars~308 tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Testing iOS Code
bitwarden/ios
Official
Write tests, add test coverage, unit test, or add missing tests for Bitwarden iOS.
694 GitHub stars~1.8k tokensUpdated yesterday
Testing & QAAuto-check passed

Questions about Xcodebuild Testing

What does Xcodebuild Testing do?

Run unit tests, UI tests, or specific test cases for VivaDicta using xcodebuild command-line tool. Xcodebuild Testing is an agent skill from n0an/VivaDicta.

When should I use Xcodebuild Testing?

Xcodebuild Testing fits situations like: tasks that involve Test generation; tasks that involve Unit testing.

How do I install Xcodebuild Testing in Claude Code?

Run `npx skills add n0an/VivaDicta --skill xcodebuild-testing -a claude-code`. Or copy the skill folder (.agents/skills/xcodebuild-testing in n0an/VivaDicta) into .claude/skills/xcodebuild-testing in your project. Claude Code loads it when a task matches its description.

How do I install Xcodebuild Testing in Codex?

Run `npx skills add n0an/VivaDicta --skill xcodebuild-testing -a codex`. Or copy the skill folder (.agents/skills/xcodebuild-testing in n0an/VivaDicta) into .agents/skills/xcodebuild-testing in your project. Codex loads it when a task matches its description.

Can I use Xcodebuild Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add n0an/VivaDicta --skill xcodebuild-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/xcodebuild-testing, .gemini/skills/xcodebuild-testing, .github/skills/xcodebuild-testing and .opencode/skills/xcodebuild-testing in your project.

What does Xcodebuild Testing need to run?

Going by SKILL.md and its folder, Xcodebuild Testing needs the command-line tools its instructions call (xcodebuild, xcrun and brew).

Does Xcodebuild Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Xcodebuild Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Xcodebuild Testing use?

Xcodebuild Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Xcodebuild Testing use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Xcodebuild Testing?

Skills that share tags, products or a category with Xcodebuild Testing: Adk Verify Snippets (google/adk-python, 22k stars), Hermetic Python Unit Tests (dimensionalOS/dimos, 4.6k stars), OpenROAD Module Test Adder (The-OpenROAD-Project/OpenROAD, 3.2k stars) and Concept Page Test Writer (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Xcodebuild Testing?

n0an (a GitHub user) maintains it in n0an/VivaDicta, which has 126 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 5, 2026.

Source: n0an/VivaDicta on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Xcodebuild Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Xcodebuild Testing

Related Skills

Skill Flow

1. Determine Test Scope

Path A: Run All Tests

2A. Run Full Test Suite

Path B: Run Specific Test

2B. Identify Test Target

3B. Run Specific Test

Path C: Run Test Class

2C. Identify Test Class

3C. Run All Tests in Class

Path D: Run with Log Capture

2D. Start Log Capture Session

3D. Run Tests

4D. Stop Log Capture and Analyze

Common Workflows

Quick Test Run During Development

Test Run with Results Saved

Run Tests on Different Simulator

Run Only Failed Tests from Previous Run

Parallel Test Execution

Test Run with Code Coverage

Debug Test Failures with Screenshots

Troubleshooting

Best Practices

Files

Compare with similar skills

Similar skills

More from n0an/VivaDicta

Related

Questions about Xcodebuild Testing