Detect defensive programming anti-patterns that cause silent failures.
npx skills add https://github.com/archibate/archibate-skills --skill anti-defensive
Please help me install this Agent Skill. Skill: anti-defensive Source: https://github.com/archibate/archibate-skills/tree/main/skills/anti-defensive Command: npx skills add https://github.com/archibate/archibate-skills --skill anti-defensive
Defensive programming patterns often hide errors, fabricate data, and allow silent failures that make bugs harder to detect and fix; this guide helps reviewers and developers identify and replace those anti-patterns with fail-fast, honest behavior.
Ask the assistant to review the provided function for defensive programming anti-patterns and recommend fail-fast replacements with specific code changes.
High-intent search queries and answers about installing and using this skill.
Detect defensive programming anti-patterns by reviewing code for exception swallowing, fabricated defaults, unnecessary null checks, and compatibility shims. This process highlights silent failures and recommends explicit fail-fast replacements to correct them.
Fail-fast programming exposes errors immediately by raising explicit exceptions, while defensive programming hides errors through fabricated defaults and catch-all handlers. Fail-fast makes bugs easier to detect, whereas defensive patterns cause silent failures.
Stop silent errors and exception swallowing during a code review by applying a fail-fast checklist that identifies catch-all handlers. Replace them with explicit error raising and validate inputs at system boundaries instead of internally.
Avoid defensive programming in internal application logic when you can trust internal contracts. Over-validation and unnecessary null checks inside trusted boundaries hide bugs; instead, validate data only at external boundaries and let internal calls fail fast.
Yes, you can apply this fail-fast approach to automated pull request audits and static analysis. It provides review checklists and explicit remediation steps to identify anti-patterns like type coercion and fabricated defaults in internal logic.
nilleReview code diffs for correctness, security, and conventions.
zm2231Refactor code to improve quality, readability, and maintainability.
IndustrialAnalyze code for security vulnerabilities and performance issues.
chapzinIdentify code quality issues and anti-patterns in pull request reviews.
