{"enrichment":{"faq":[{"a":"ios-chaos-monkey helps developers identify hidden concurrency issues in Swift iOS applications by simulating chaotic conditions and stress scenarios. It detects data races, deadlocks, and thread-safety violations that traditional testing often misses, enabling more resilient mobile code.","q":"What does ios-chaos-monkey help find and fix in iOS crash debugging?"},{"a":"ios-chaos-monkey audits memory management patterns in Swift iOS code to identify retain cycles, use-after-free crashes, and memory leaks. By stress-testing concurrent access patterns and async/await flows, it reveals memory corruption issues that surface under chaotic load conditions rather than normal execution.","q":"How does ios-chaos-monkey detect memory leaks and retain cycles?"},{"a":"Yes. ios-chaos-monkey audits async/await and structured concurrency for cancellation leaks, continuation leaks, and actor isolation problems. It helps identify MainActor blocking, resource exhaustion in concurrent tasks, and Swift Sendable data race violations that emerge under stress.","q":"Can ios-chaos-monkey audit async/await and structured concurrency?"},{"a":"ios-chaos-monkey stress-tests file I/O and SwiftData persistence layers for corruption and context misuse crashes. It simulates chaotic conditions to expose race conditions in CoreData cross-thread access and SwiftData concurrency violations that normal testing overlooks.","q":"Does ios-chaos-monkey stress-test file I/O and SwiftData?"},{"a":"ios-chaos-monkey supports writing proof-of-crash tests before implementing fixes using TDD. Write tests that reproduce concurrency bugs under chaotic conditions, then implement fixes to pass them\u2014enabling confident refactoring of thread-safety violations and async/await deadlocks.","q":"How can I use ios-chaos-monkey with test-driven development?"},{"a":"ios-chaos-monkey is released under the MIT license, making it free to use, modify, and distribute in both open-source and commercial iOS projects.","q":"What license does ios-chaos-monkey use?"}],"shadow_tags":["crash-hunting","concurrency-safety","memory-management","thread-safety","persistence-layer","async-patterns","resource-leaks","test-driven-debugging"],"summary_rewrite":"ios-chaos-monkey helps developers identify hidden concurrency issues in Swift iOS applications by simulating chaotic conditions and stress scenarios. It detects data races, deadlocks, and thread-safety violations that traditional testing often misses, enabling more resilient mobile code."},"files":[{"bytes":9286,"path":"skills/.experimental/ios-chaos-monkey/SKILL.md","sha256":"7dc6c7b9cb5c66ca1e3a27a36bdcbd3c9d8118b274f51ed3d28c3f349aae411d","url":"https://skillfed.io/files/pproenca/dot-skills/ios-chaos-monkey/7354ebdb/SKILL.md"}],"id":"pproenca/dot-skills/ios-chaos-monkey","links":{"html":"https://skillfed.io/pproenca/dot-skills/ios-chaos-monkey","md":"https://skillfed.io/pproenca/dot-skills/ios-chaos-monkey.md","repo":"https://github.com/pproenca/dot-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":14,"language":"Shell","last_updated":"2026-07-24","license":"MIT","name":"ios-chaos-monkey","publisher":"pproenca","stars":182},"relations":{"similar":[{"id":"CharlesWiltgen/Axiom/axiom-concurrency"},{"id":"CharlesWiltgen/Axiom/axiom-audit-concurrency"},{"id":"rshankras/claude-code-apple-skills/concurrency-patterns"},{"id":"CharlesWiltgen/Axiom/axiom-audit-swiftdata"},{"id":"AvdLee/Swift-Concurrency-Agent-Skill/swift-concurrency"},{"id":"CharlesWiltgen/Axiom/axiom-audit-memory"},{"id":"softspark/ai-toolkit/swift-patterns"},{"id":"rshankras/claude-code-apple-skills/profiling"},{"id":"affaan-m/ECC/swift-actor-persistence"},{"id":"dpearson2699/swift-ios-skills/debugging-instruments"}]},"slug":{"owner":"pproenca","repo":"dot-skills","skill":"ios-chaos-monkey"},"version":"7354ebdb"}