skills.rest
cruisediary
cruisediaryCOMMUNITY
Explore all skills by this author →
GitHub

crash-risk-audit

Detect crash-prone Swift patterns like force unwraps and fatalError in iOS/macOS projects.

13|1|Updated Mar 29, 2026
Search Tags:#swift#code-quality#guidelines#static-analysis#app-store#crash
One-click install
npx skills add https://github.com/cruisediary/apple-app-review-skills --skill crash-risk-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crash-risk-audit
Source: https://github.com/cruisediary/apple-app-review-skills/tree/main/skills/quality/crash-risk-audit
Command: npx skills add https://github.com/cruisediary/apple-app-review-skills --skill crash-risk-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects crash-prone Swift patterns such as force unwraps, forced casts, force try, and fatalError usage that can cause unrecoverable crashes during App Store submission.

Core Features & Use Cases

  • Detects force unwraps (!) and force casts (as!) in Swift source files.
  • Flags force try and fatalError usage that may crash in edge-case data paths.
  • Highlights UI updates on background threads that mutate UI to prevent race conditions during review.

Quick Start

Run the Crash Risk Audit on your Swift project to identify force unwraps, force casts, force try, and fatalError usages that could crash during App Store review.

Frequently Asked Questions about crash-risk-audit

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

FAQPage Schema
How do I find force unwrap and force cast crash risks in Swift code before App Store review?▼

A crash risk audit scans Swift source files to detect force unwraps, forced casts, force try, and fatalError usages that cause unrecoverable crashes during App Store submission. It produces prioritized findings for remediation.

Why does my iOS app crash during App Store review?▼

App Store review crashes often stem from crash-prone Swift patterns like force unwraps, forced casts, and fatalError usage in edge-case data paths. A static audit identifies these specific patterns across your source files.

Can I scan my iOS project for UI updates on background threads that cause race conditions?▼

Yes, you can scan iOS Swift projects to highlight background thread UI mutations that cause race conditions during review. The audit produces prioritized findings for these thread safety violations.

What is the best way to detect fatalError and force try usage in a macOS Swift project?▼

The best way to detect fatalError and force try usage is a grep-like pattern search across macOS Swift sources. This audit flags these crash-prone patterns that may crash in edge-case data paths.

Does this crash risk audit require any external dependencies to run on Swift source files?▼

No external dependencies are required to run this crash risk audit. It relies on grep-like pattern searches directly across your Swift sources to identify crash-prone patterns and output prioritized findings.

Related Skills

Explore More Software Engineering Skills→
n0rvynn0rvyn
1

code-audit

Audit Swift projects for security, concurrency, accessibility, and SwiftUI issues.

Community
Advanced
tanujsutariatanujsutaria
1

lint-validator

Lint changed Swift files with SwiftLint and report violations.

Community
Advanced
amanhsnamanhsn

code-reviewer

Analyze pull requests for complexity, risk, and code quality issues.

Community
Advanced
AutisticAFAutisticAF
4

swift-concurrency-patterns

Diagnose Swift concurrency bugs and data races in asynchronous code.

Community
Advanced