axiom-audit-codable

Name: axiom-audit-codable
Availability: InStock
Author: dengnaichen

Analyze Swift Codable implementations for serialization anti-patterns and structural risks.

34|2|Updated Mar 16, 2026

Search Tags:#json #swift #serialization #code-audit #codable #data-safety

Ready to run

npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-codable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: axiom-audit-codable
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-audit-codable
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-codable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies critical safety violations in Swift Codable implementations, such as silent data loss, production crashes, and revenue leaks caused by improper serialization patterns.

Core Features & Use Cases

Anti-Pattern Detection: Automatically flags dangerous practices like manual JSON string building, try? swallowing errors, and missing date strategies.
Architecture Mapping: Provides a clear overview of serialization boundaries and decoder configurations across your codebase.
Use Case: Use this during a code review or refactoring phase to ensure your API models are robust against server-side schema changes and that your persistence layer is not silently failing.

Quick Start

Run the axiom-audit-codable skill to perform a full serialization audit on the current repository.

Frequently Asked Questions about axiom-audit-codable

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

FAQPage Schema

How do I detect silent data loss in Swift Codable implementations?▼

Run a Swift Codable serialization audit to flag anti-patterns like manual JSON string building and try? error swallowing that cause silent data loss. This analysis evaluates manual decoding logic and decoder strategy consistency to prevent production crashes and revenue leaks.

What are common Swift Codable serialization anti-patterns that cause runtime crashes?▼

Common Swift Codable serialization anti-patterns include manual JSON string building, using try? to swallow decoding errors, and omitting date strategies. These structural risks cause silent data loss and runtime crashes across network and persistence boundaries when server-side schemas change.

How do I audit my Swift API models for decoder strategy consistency?▼

Audit Swift API models for decoder strategy consistency by evaluating manual encoding and decoding logic across your codebase. This mapping provides a clear overview of serialization boundaries and validates type safety to ensure your persistence layer is not silently failing.

Does this Codable audit work for both network and persistence boundaries?▼

Yes, this Codable audit works for both network and persistence boundaries. It analyzes structural risks and potential silent data loss across these serialization boundaries, validating type safety and error handling to ensure production-grade data serialization against server-side schema changes.

When do I need to audit my Swift Codable models for type safety?▼

You need to audit Swift Codable models for type safety during code review or refactoring phases. This ensures your API models are robust against server-side schema changes and verifies that your persistence layer is not silently failing during data serialization.