apple-text-audit

Audit Apple Text code for TextKit fallback risks and deprecated APIs.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sitapix/apple-text --skill apple-text-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apple-text-audit
Source: https://github.com/sitapix/apple-text/tree/main/skills/apple-text-audit
Command: npx skills add https://github.com/sitapix/apple-text --skill apple-text-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify TextKit fallback risks, editing lifecycle bugs, and deprecated API usage in Apple Text code.

Core Features & Use Cases

  • Inline audit of TextKit usage across UITextView and NSTextView, with focus on fallback paths and lifecycle correctness.
  • Detect deprecated API usage and potential Writing Tools integration issues that could cause regressions.
  • Use Case: Imagine a project where a UITextView switches to TextKit 1 unexpectedly; run this audit to surface the roots and suggest fixes.

Quick Start

Run an inline audit across the current workspace to surface TextKit risks and suggested fixes.

Frequently Asked Questions about apple-text-audit

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

FAQPage Schema
How do I audit my iOS app for TextKit fallback risks and deprecated APIs?

To audit for TextKit fallback risks, scan your codebase to identify deprecated API usage and unexpected TextKit 1 fallbacks in UITextView and NSTextView components, then review the suggested fixes to ensure lifecycle correctness.

What causes a UITextView to unexpectedly switch to TextKit 1 during runtime?

A UITextView may switch to TextKit 1 unexpectedly due to specific legacy API usage or editing lifecycle bugs. Running a targeted code audit surfaces these root causes and highlights the deprecated calls triggering the fallback.

How do I check my NSTextView code for editing lifecycle bugs?

Check for NSTextView editing lifecycle bugs by running an inline audit across your workspace to evaluate TextKit usage paths, detect deprecated methods, and verify the correctness of text editing state transitions.

Does this audit detect potential Writing Tools integration issues in Apple Text code?

Yes, the audit detects potential Writing Tools integration issues by scanning Apple Text code for deprecated APIs and TextKit fallback paths that could cause regressions when integrating modern text editing features.

What do I need to run an inline TextKit code audit?

You need a codebase context or workspace environment to run the inline TextKit audit. The scan uses an internal checklist to evaluate UITextView and NSTextView components, or delegates to a textkit-auditor agent if available.