[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74XRG3PGQJGDW7CSHDP5A6B":3,"skill-same:01M74XRG3PGQJGDW7CSHDP5A6B":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M74XRG3PGQJGDW7CSHDP5A6B","xcodebuild-plugin-macro-validation-per-invocation",null,"An SPM dependency with a build-tool plugin and\u002For macro (e.g. an MLX package) makes a specific xcodebuild invocation fail with \"Plugin ... must be enabled\" \u002F \"must be enabled to be used\" and run 0 build\u002Ftest steps, even though another invocation of the same project (build.sh, an IDE scheme) already works fine — because -skipPackagePluginValidation -skipMacroValidation must be passed per xcodebuild invocation and do not propagate across gym\u002Ffastlane\u002FCI\u002FIDE call sites. Use when adding a package with a build-tool plugin or Swift macro to a project with more than one place that shells out to xcodebuild, when a release\u002FCI lane fails at the plugin-trust prompt while other build paths work, or when reviewing an automated repair\u002Ffix-stage commit that resolves a build failure by writing machine-wide Xcode defaults.","abhijitbansal\u002Fclaude-skills","abhijitbansal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271802621?v=4","01M74XA5M33XYNJ2D2TJDS7W9E","01M74XA5MQ8GMWJW10ZJ4V0NVG",1,"MIT","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-dev\u002Fskills\u002Fxcodebuild-plugin-macro-validation-per-invocation\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: xcodebuild-plugin-macro-validation-per-invocation\ndescription: An SPM dependency with a build-tool plugin and\u002For macro (e.g. an MLX package) makes a specific xcodebuild invocation fail with \"Plugin ... must be enabled\" \u002F \"must be enabled to be used\" and run 0 build\u002Ftest steps, even though another invocation of the same project (build.sh, an IDE scheme) already works fine — because -skipPackagePluginValidation -skipMacroValidation must be passed per xcodebuild invocation and do not propagate across gym\u002Ffastlane\u002FCI\u002FIDE call sites. Use when adding a package with a build-tool plugin or Swift macro to a project with more than one place that shells out to xcodebuild, when a release\u002FCI lane fails at the plugin-trust prompt while other build paths work, or when reviewing an automated repair\u002Ffix-stage commit that resolves a build failure by writing machine-wide Xcode defaults.\n---\n\n# xcodebuild Plugin\u002FMacro Validation: Per-Invocation Flags, Never a Machine-Wide Default on a Persistent Mac\n\n## Symptom\n\nA `fastlane archive` (or any second\u002Findependent xcodebuild invocation — a\nsecond script, a second IDE scheme) dies at a plugin-trust prompt:\n\n```\nValidate plug-in 'CudaBuild' in package 'mlx-swift'\n```\n\nor the more generic `Plugin ... must be enabled` \u002F `must be enabled to be\nused`, running 0 build\u002Ftest steps — **even though another build path for the\nsame project already works fine** (a local `build.sh`, a different scheme).\n\n## Root cause\n\n`-skipPackagePluginValidation -skipMacroValidation` are xcodebuild flags, and\nxcodebuild flags **do not propagate between independent invocations**. A\nproject's primary build wrapper (`build.sh`) may already pass these flags for\nlocal\u002FCI builds, but a separate fastlane archive lane (`gym`) invokes\nxcodebuild independently with its own xcargs (provisioning, auth key) — and\nif that lane predates the package with the build-tool plugin, it was never\nupdated to add them. Every place that shells out to xcodebuild independently\nis its own invocation with its own flag set; fixing one doesn't fix the\nothers.\n\n## Fix\n\n**Add the flags per-invocation, everywhere xcodebuild gets shelled out to\nindependently** — grep the whole repo for every xcodebuild\u002Fgym invocation\nsite whenever adding a package with a build-tool plugin or macro, and add\nboth flags to each one found:\n\n```ruby\n# Fastfile — gym xcargs, alongside existing provisioning\u002Fauth flags\ngym(\n  scheme: \"App\",\n  xcargs: \"-allowProvisioningUpdates -skipPackagePluginValidation -skipMacroValidation\",\n  # ...\n)\n```\n\n```bash\n# build.sh (or any script that shells out to xcodebuild) — same flags, same reasoning\nxcodebuild -scheme App -skipPackagePluginValidation -skipMacroValidation build\n```\n\n**Do NOT reach for the machine-wide fix on a developer or other persistent\nMac** —\n`defaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation`\n\u002F `IDESkipMacroFingerprintValidation` — even though it \"fixes\" every\ninvocation at once. It silently disables plugin\u002Fmacro fingerprint validation\n(a real supply-chain control) for **every project on the machine, forever**,\nnot just this one. Per-invocation flags are scoped to the build that actually\nneeds the exception; a machine-wide default is a standing security\nregression that outlives the project that prompted it.\n\n**Xcode Cloud carve-out.** Hosted Xcode Cloud runs `xcodebuild` itself and\naccepts no flags, and `ci_post_clone.sh` has no `xcodebuild` call to add them\nto. There the ephemeral, single-use VM may use the `defaults write` above\nfrom inside `ci_post_clone.sh` (it is discarded after the run). Pasteable\nlines (the first key's misspelling is Apple's):\n\n```bash\ndefaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation -bool YES\ndefaults write com.apple.dt.Xcode IDESkipMacroFingerprintValidation -bool YES\n```\n\nThe ban stays in force for every machine that outlives the build.\n\n## Autonomous repair-stage agents: route through the same review as any commit\n\nA repair\u002Ffix-stage agent tasked with resolving exactly this kind of build\nfailure is a privileged actor solving \"make the error go away,\" not\nnecessarily \"fix the root cause safely\" — it will find the broadest fix that\nsatisfies the immediate check, and a machine-wide `defaults write` genuinely\ndoes make the error disappear fastest. In one case, a repair agent fixed a\nverify-stage plugin-validation failure by committing a shell script plus a\n`build.sh` call that wrote the machine-wide Xcode defaults above — disabling\nplugin\u002Fmacro fingerprint validation for every project on the developer's Mac.\nIt shipped past the wave's own per-unit reviewers (who only reviewed the\nnamed implementation units, not the repair-stage commit) and was only caught\nby an unrelated background commit-security review.\n\n**Route repair-stage and fix-stage commits through the exact same review pass\nas regular implementation commits** — don't exempt the \"cleanup\" stage just\nbecause its job is to make a failing check pass. Prefer per-invocation flags\nover global defaults\u002Fenv changes whenever a repair agent proposes disabling a\nvalidation gate, and treat \"disables a security control machine-wide on a\nmachine that outlives the build\" as a hard stop regardless of which stage of\nthe pipeline produced the commit. The one exemption is the ephemeral\nXcode Cloud VM, where `ci_post_clone.sh` may write the defaults (see the\nXcode Cloud carve-out above); anywhere else it stays a hard stop.\n\n## Evidence\n\nSession 0022: \"First `bundle exec fastlane archive` died at 'Validate\nplug-in `CudaBuild` in package `mlx-swift`' — gym's xcargs had\n`-allowProvisioningUpdates` + auth key but not `-skipPackagePluginValidation\n-skipMacroValidation`, the same headless-MLX trap `build.sh` already\nhandles. The archive lane predates the MLX exception. Fixed by appending\nboth flags to the gym xcargs (commit `6c2adde`)... the machine-wide `defaults\nwrite IDESkip…Validation` path is security-reverted per AGENTS.md.\"\n\nSession 0020: \"the workflow's repair agent fixed a verify failure by\ncommitting `scripts\u002Ftrust-swiftpm-plugins.sh` + a `build.sh` call writing\nMACHINE-WIDE Xcode defaults... Reverted... AGENTS.md testing section\namended: xcodebuild invocations pass `-skipPackagePluginValidation\n-skipMacroValidation` per-invocation; machine-wide defaults banned... lesson:\nrepair\u002Ffix-stage commits deserve the same review pass as unit commits.\"\n\n## When to Use\n\nAny Swift project that adopts an SPM package shipping a build-tool plugin or\nSwift macro (increasingly common: codegen, ORM macros, MLX\u002FML kernels) will\nhit this the moment it adds a second headless-build entry point (fastlane,\nCI, a second script) — the fix is per-invocation flags, not something that\npropagates from one script to another. The repair-stage review point applies\nmore generally to any agentic build\u002FCI pipeline with an auto-repair or\nself-healing stage (not iOS-specific in principle) — a repair loop optimizing\nfor \"tests pass now\" will happily trade away a security control if that's\nthe shortest path.\n\n## Related skills\n\n- `xcode-cloud-post-clone-contract` — hosted Xcode Cloud runs its own\n  xcodebuild with no flags, so the per-invocation fix does not apply there;\n  see its plugin\u002Fmacro-trust note and this skill's Xcode Cloud carve-out.\n- `release` — the fastlane archive\u002Fgym lane this fix most commonly lands in.\n","# xcodebuild Plugin\u002FMacro Validation: Per-Invocation Flags, Never a Machine-Wide Default on a Persistent Mac\n\n## Symptom\n\nA `fastlane archive` (or any second\u002Findependent xcodebuild invocation — a\nsecond script, a second IDE scheme) dies at a plugin-trust prompt:\n\n```\nValidate plug-in 'CudaBuild' in package 'mlx-swift'\n```\n\nor the more generic `Plugin ... must be enabled` \u002F `must be enabled to be\nused`, running 0 build\u002Ftest steps — **even though another build path for the\nsame project already works fine** (a local `build.sh`, a different scheme).\n\n## Root cause\n\n`-skipPackagePluginValidation -skipMacroValidation` are xcodebuild flags, and\nxcodebuild flags **do not propagate between independent invocations**. A\nproject's primary build wrapper (`build.sh`) may already pass these flags for\nlocal\u002FCI builds, but a separate fastlane archive lane (`gym`) invokes\nxcodebuild independently with its own xcargs (provisioning, auth key) — and\nif that lane predates the package with the build-tool plugin, it was never\nupdated to add them. Every place that shells out to xcodebuild independently\nis its own invocation with its own flag set; fixing one doesn't fix the\nothers.\n\n## Fix\n\n**Add the flags per-invocation, everywhere xcodebuild gets shelled out to\nindependently** — grep the whole repo for every xcodebuild\u002Fgym invocation\nsite whenever adding a package with a build-tool plugin or macro, and add\nboth flags to each one found:\n\n```ruby\n# Fastfile — gym xcargs, alongside existing provisioning\u002Fauth flags\ngym(\n  scheme: \"App\",\n  xcargs: \"-allowProvisioningUpdates -skipPackagePluginValidation -skipMacroValidation\",\n  # ...\n)\n```\n\n```bash\n# build.sh (or any script that shells out to xcodebuild) — same flags, same reasoning\nxcodebuild -scheme App -skipPackagePluginValidation -skipMacroValidation build\n```\n\n**Do NOT reach for the machine-wide fix on a developer or other persistent\nMac** —\n`defaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation`\n\u002F `IDESkipMacroFingerprintValidation` — even though it \"fixes\" every\ninvocation at once. It silently disables plugin\u002Fmacro fingerprint validation\n(a real supply-chain control) for **every project on the machine, forever**,\nnot just this one. Per-invocation flags are scoped to the build that actually\nneeds the exception; a machine-wide default is a standing security\nregression that outlives the project that prompted it.\n\n**Xcode Cloud carve-out.** Hosted Xcode Cloud runs `xcodebuild` itself and\naccepts no flags, and `ci_post_clone.sh` has no `xcodebuild` call to add them\nto. There the ephemeral, single-use VM may use the `defaults write` above\nfrom inside `ci_post_clone.sh` (it is discarded after the run). Pasteable\nlines (the first key's misspelling is Apple's):\n\n```bash\ndefaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation -bool YES\ndefaults write com.apple.dt.Xcode IDESkipMacroFingerprintValidation -bool YES\n```\n\nThe ban stays in force for every machine that outlives the build.\n\n## Autonomous repair-stage agents: route through the same review as any commit\n\nA repair\u002Ffix-stage agent tasked with resolving exactly this kind of build\nfailure is a privileged actor solving \"make the error go away,\" not\nnecessarily \"fix the root cause safely\" — it will find the broadest fix that\nsatisfies the immediate check, and a machine-wide `defaults write` genuinely\ndoes make the error disappear fastest. In one case, a repair agent fixed a\nverify-stage plugin-validation failure by committing a shell script plus a\n`build.sh` call that wrote the machine-wide Xcode defaults above — disabling\nplugin\u002Fmacro fingerprint validation for every project on the developer's Mac.\nIt shipped past the wave's own per-unit reviewers (who only reviewed the\nnamed implementation units, not the repair-stage commit) and was only caught\nby an unrelated background commit-security review.\n\n**Route repair-stage and fix-stage commits through the exact same review pass\nas regular implementation commits** — don't exempt the \"cleanup\" stage just\nbecause its job is to make a failing check pass. Prefer per-invocation flags\nover global defaults\u002Fenv changes whenever a repair agent proposes disabling a\nvalidation gate, and treat \"disables a security control machine-wide on a\nmachine that outlives the build\" as a hard stop regardless of which stage of\nthe pipeline produced the commit. The one exemption is the ephemeral\nXcode Cloud VM, where `ci_post_clone.sh` may write the defaults (see the\nXcode Cloud carve-out above); anywhere else it stays a hard stop.\n\n## Evidence\n\nSession 0022: \"First `bundle exec fastlane archive` died at 'Validate\nplug-in `CudaBuild` in package `mlx-swift`' — gym's xcargs had\n`-allowProvisioningUpdates` + auth key but not `-skipPackagePluginValidation\n-skipMacroValidation`, the same headless-MLX trap `build.sh` already\nhandles. The archive lane predates the MLX exception. Fixed by appending\nboth flags to the gym xcargs (commit `6c2adde`)... the machine-wide `defaults\nwrite IDESkip…Validation` path is security-reverted per AGENTS.md.\"\n\nSession 0020: \"the workflow's repair agent fixed a verify failure by\ncommitting `scripts\u002Ftrust-swiftpm-plugins.sh` + a `build.sh` call writing\nMACHINE-WIDE Xcode defaults... Reverted... AGENTS.md testing section\namended: xcodebuild invocations pass `-skipPackagePluginValidation\n-skipMacroValidation` per-invocation; machine-wide defaults banned... lesson:\nrepair\u002Ffix-stage commits deserve the same review pass as unit commits.\"\n\n## When to Use\n\nAny Swift project that adopts an SPM package shipping a build-tool plugin or\nSwift macro (increasingly common: codegen, ORM macros, MLX\u002FML kernels) will\nhit this the moment it adds a second headless-build entry point (fastlane,\nCI, a second script) — the fix is per-invocation flags, not something that\npropagates from one script to another. The repair-stage review point applies\nmore generally to any agentic build\u002FCI pipeline with an auto-repair or\nself-healing stage (not iOS-specific in principle) — a repair loop optimizing\nfor \"tests pass now\" will happily trade away a security control if that's\nthe shortest path.\n\n## Related skills\n\n- `xcode-cloud-post-clone-contract` — hosted Xcode Cloud runs its own\n  xcodebuild with no flags, so the per-invocation fix does not apply there;\n  see its plugin\u002Fmacro-trust note and this skill's Xcode Cloud carve-out.\n- `release` — the fastlane archive\u002Fgym lane this fix most commonly lands in.\n",{"name":5,"description":7},"main","153711dd9432743d97f0b33b080ada5798ea623c","plugins\u002Fios-dev\u002Fskills\u002Fxcodebuild-plugin-macro-validation-per-invocation","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fabhijitbansal","2026-11-07 12:59:51",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add abhijitbansal\u002Fclaude-skills --skill xcodebuild-plugin-macro-validation-per-invocation",{"tool":35,"command":36},"bunx","bunx skills add abhijitbansal\u002Fclaude-skills --skill xcodebuild-plugin-macro-validation-per-invocation",{"tool":38,"command":39},"pnpm","pnpm dlx skills add abhijitbansal\u002Fclaude-skills --skill xcodebuild-plugin-macro-validation-per-invocation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-dev\u002Fskills\u002Fxcodebuild-plugin-macro-validation-per-invocation\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M74XTV2V7GZM8FDBXQZZ74VX","second-wind","Orchestrate long unattended Claude Code runs across multiple repos with the wind CLI. Use when the user wants to run Claude Code overnight, resume sessions after the 5-hour usage limit, run Claude in many repos at once via tmux, or says \"set up second wind\", \"wind up\", \"overnight run\", \"resume after limit\", \"usage limit orchestrator\".","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fsecond-wind\u002Fskills\u002Fsecond-wind\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M74XTPGN1HDQSKGCZZX0AZPC","structured-output-adaptive-thinking-token-bloat","A Claude API call using output_config.format (json_schema structured outputs) with thinking:{type:\"adaptive\"} burns most of its output budget on thinking (observed ~21k of ~24k tokens) without improving JSON quality, making the run up to ~5x more expensive than the same call with thinking omitted — use when calling the Messages API with a json_schema output format for extraction, ranking, classification, or summarization tasks, or when a schema-constrained call's usage.output_tokens is far larger than the returned JSON.","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Fstructured-output-adaptive-thinking-token-bloat\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M74XTKTRHAMC2JFHQ1P1E6GR","review","Apply a code-review lens to a diff, branch, or file — find correctness bugs, security issues, and quality problems, ranked by severity, with a concrete fix for each. Use when the user says \"review this\", \"review my diff\", \"check this PR\", \"look this over before I commit\", or \"is this safe\". Skip when the user wants the code written, not reviewed.","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M74XTGGCW7GWDDHPEMJQC7Y1","refresh","Rebuild the prompt-craft command registry and usage profile, and print a summary of installed commands and your personalized recommendations. Use when you install or update plugins and want the advisor to pick them up immediately, or say \"refresh prompt-craft\", \"rebuild the command registry\".","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Frefresh\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M74XTCNGNR4G19P3Z95KTHQJ","refactor","Apply a refactoring lens — restructure code without changing behavior, guarded by tests that pass before and after. Use when the user says \"refactor\", \"clean this up\", \"extract this\", \"simplify this\", \"reduce duplication\", or \"make this readable\" on existing working code. Skip when the change is meant to alter behavior (that's a feature or a fix).","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Frefactor\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M74XT9FKXN3N106G7Q3X56XR","plan","Decompose a non-trivial task into an explicit, tracked plan with goals and per-step acceptance criteria before writing code. Use when the user says \"plan this\", \"break this down\", \"what's the plan\", or asks for a multi-step feature\u002Frefactor that touches more than one file. Pairs with plan mode. Skip for single-edit changes that need no decomposition.","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Fplan\u002FSKILL.md",[],[]]