objc-xrpc-contract-audit

You can audit Objective-C XRPC endpoint implementations by scanning the code directory to analyze registration signals, authentication checks, input validation patterns, and error handling structures, outputting a contract compliance summary.

XRPC endpoint regressions and interop bugs in Objective-C code are caused by lexicon drift, missing authentication checks, invalid parameter validation, or unstable error shapes that deviate from the defined response schema.

XRPC contract auditing detects lexicon drift by analyzing the Objective-C code for response schema conformance, verifying that the endpoint's error shapes and parameter validation patterns match the expected XRPC contract specifications.

Yes, you can review parameter validation and authentication expectations by scanning the directory, where the audit analyzes the code for registration signals and authentication check patterns to verify API compliance.

The best way to find the cause of unexpected XRPC endpoint errors after a code change is to run a contract audit that pinpoints deviations in authentication, parameter validation, and stable error shapes.

No external dependencies are required to scan your Objective-C project for XRPC contract issues, as the skill operates standalone using internal scripts and references to output the audit summary to a local directory.