xcodebuildmcp-packaging-resource-review

Review XcodeBuildMCP packaging guardrails across files, schemas, and manifests.

6.2k|312|Updated Mar 9, 2025
One-click install
npx skills add https://github.com/getsentry/XcodeBuildMCP --skill xcodebuildmcp-packaging-resource-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xcodebuildmcp-packaging-resource-review
Source: https://github.com/getsentry/XcodeBuildMCP/tree/main/.agents/skills/xcodebuildmcp-packaging-resource-review
Command: npx skills add https://github.com/getsentry/XcodeBuildMCP --skill xcodebuildmcp-packaging-resource-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Review guardrails for packaging, resource-root integrity, and portable macOS distribution changes within XcodeBuildMCP artifacts, helping ensure builds are reproducible and safe to share.

Core Features & Use Cases

  • Review scope is default to review-only, preventing code edits unless explicitly requested.
  • Inspect critical files such as package.json, scripts/copy-build-assets.js, scripts/package-macos-portable.sh, scripts/build-website-manifest.mjs, schemas/, manifests/, skills/, and bundled/ when present.
  • Guardrails and validation steps include ensuring required runtime resources are published, portable layout consistency, and environment hygiene during packaging.

Quick Start

Use npm run build to prepare artifacts, then execute npm run verify:portable and npx skill-check .agents/skills/xcodebuildmcp-packaging-resource-review to validate packaging guardrails.

Frequently Asked Questions about xcodebuildmcp-packaging-resource-review

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

FAQPage Schema
How do I validate portable macOS build packaging integrity for XcodeBuildMCP?

Portable distribution reviews inspect package.json, scripts/copy-build-assets.js, scripts/package-macos-portable.sh, scripts/build-website-manifest.mjs, schemas, manifests, skills, and bundled directories to ensure required runtime resources are correctly published and included.

What packaging guardrails should I check before distributing a portable macOS build?

The default review scope is review-only, preventing code edits unless explicitly requested. Guardrails enforce that required runtime resources are published, portable layout consistency is maintained, and environment hygiene is upheld during packaging to ensure reproducible artifacts.

Why does my portable macOS build fail the verify:portable check?

The verify:portable check fails when packaging guardrails detect missing runtime resources in manifests or bundled directories, inconsistent portable layout structures, or environment hygiene issues that compromise reproducible and safe-to-share macOS distribution artifacts.

Can I use this packaging review workflow to fix broken manifest or schema files?

No, the default review scope is review-only, preventing code edits unless explicitly requested. It inspects manifests, schemas, and packaging scripts to identify integrity issues without automatically modifying the detected guardrail violations.

When do I need to review schemas and manifests for portable macOS distribution?

Review schemas and manifests when preparing portable macOS distribution changes, running npm run build, or executing verify:portable checks to ensure required runtime resources are correctly included and packaging integrity is maintained for reproducible builds.