xcode-compilation-analyzer skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
xcode-compilation-analyzer is agent-read markdown (skill) from omarshahine/homeclaw: Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Xcode Compilation Analyzer Use this skill when compile time, not just general project configuration, looks like the bottleneck. ## Core Rules - Start from evidence, ideally a recent `.build-benchmark/` artifact or raw timing-summary output. - Prefer analysis-only compiler flags over persistent project edits during investigation. - Rank findings by expected **wall-clock** impact, not cumulative compile-time impact. When compile tasks are heavily parallelized (sum of compile categories >> wall-clock median), note that fixing individual hotspots may improve parallel efficiency without reducing build wait time. - When the evidence points to parallelized work rather than serial bottlenecks, label recommendations as "Reduces compiler workload (parallel)" rather than "Reduces build time." - Do not edit source or build settings without explicit developer approval. ## What To Inspect - `Build Timing Summary` output from clean and incremental builds - long-running `CompileSwiftSources` or per-file compilation tasks - `SwiftEmitModule` time -- can reach 60s+ after a single-line change in large modules; if it dominates incremental builds, the module is likely too large or macro-heavy …
Read the whole file at its exact version.
How to install
mdr add omarshahine/homeclaw/xcode-compilation-analyzer@git:20260510.35d37d5mdr add omarshahine/homeclaw/xcode-compilation-analyzer@sha256:c49d8bf206d6ea2dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ek2akaa3e4suynrw)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5446 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
omarshahine/homeclaw · 173 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ek2akaa3e4suynrw GET https://markdownregistry.com/api/v1/resolve?ref=omarshahine/homeclaw/xcode-compilation-analyzer GET https://markdownregistry.com/api/v1/blob/c49d8bf206d6ea2d575dbfa95cd623b1970e796c59819cc83865bd3a15f19e65
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from omarshahine/homeclaw
Every file in omarshahine/homeclaw