cc-defensive-programming

You can audit defensive programming by running a 24-item checklist against your production code to evaluate error handling, input validation, and exception patterns. The review outputs VIOLATION, WARNING, or PASS statuses to pinpoint critical robustness issues.

Assertions verify internal invariants during development, while error handling manages runtime failures in production. This Skill applies a structured decision framework to enforce correct usage boundaries, preventing assertion misuse in live services.

Crisis triage requires a structured decision framework to prioritize defects based on risk controls and barricade design. This Skill guides reviewers through crisis triage to isolate failures and evaluate documented risk controls.

You enforce consistent error handling by applying a pattern reuse gate across modules within your codebase. This ensures uniform exception strategies and barricade design, reducing scattered or incorrect defensive coding implementations.

Yes, the defensive programming checklist applies to production code bases, libraries, and services where correctness, robustness, and barricade design matter. It audits unvalidated input and empty catch blocks across these environments.

Code reviews miss empty catch blocks and unvalidated input without a standardized auditing process. Applying a 24-item defensive coding checklist enforces structured validation checks to catch these specific robustness failures.