build-verify

Execute Xcode builds to detect compilation errors and warnings in Swift projects.

2|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/entaku0818/claude-code-settings --skill build-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-verify
Source: https://github.com/entaku0818/claude-code-settings/tree/main/docs/skills/collected/voicedocs/build-verify
Command: npx skills add https://github.com/entaku0818/claude-code-settings --skill build-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of verifying code changes by running Xcode builds, ensuring that new code doesn't introduce compilation errors or warnings.

Core Features & Use Cases

  • Automated Build Execution: Runs xcodebuild to compile your project.
  • Error and Warning Detection: Filters output to show only critical build issues.
  • Macro Validation Skipping: Includes the -skipMacroValidation flag for ComposableArchitecture projects.
  • Use Case: After adding a new feature, you can ask Claude to run a build verification to catch any immediate compilation problems before proceeding further.

Quick Start

Run a build verification for the voicedocs project.

Frequently Asked Questions about build-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Swift code changes with an Xcode build?

To verify Swift code changes, you can run an automated Xcode build that compiles the project and filters the output to show only critical compilation errors and warnings.

Does Xcode build verification work with Composable Architecture projects?

Yes, Xcode build verification works with Composable Architecture projects by including the `-skipMacroValidation` flag during the `xcodebuild` process to prevent macro-related build interruptions.

What is the best way to catch compilation errors after modifying iOS code?

The best way to catch compilation errors after modifying iOS code is to execute a build verification that runs `xcodebuild` and provides immediate feedback on whether the compilation succeeded or failed.

How do I run a build verification for my Xcode project?

You run a build verification by requesting it for your specific project, which triggers `xcodebuild` to compile the code and report any compilation errors or warnings found.

What happens if my Xcode build verification fails?

If your Xcode build verification fails, the skill reports the specific compilation errors and warnings detected, and then offers to help debug the build failure.

Why do I need to skip macro validation when building Swift projects?

You need to skip macro validation when building Swift projects using the Composable Architecture because the `-skipMacroValidation` flag is required to allow the build to compile without being blocked by macro checks.