cleanup-defensive

This Skill removes useless try/catch blocks by scanning your codebase and deleting error handling that adds no value, while preserving boundary catches in HTTP handlers and CLI entry points to maintain system stability.

Your code swallows errors because of defensive try/catch blocks that catch exceptions without handling them. This Skill identifies and removes these empty blocks, allowing errors to propagate naturally for better debugging and error handling.

Yes, this defensive code cleanup tool preserves try/catch blocks in system boundary files like HTTP handlers and CLI entry points. It only removes defensive guards and error handling that do not serve a useful role in the core logic.

The best way to clean up defensive null-checks across multiple languages is to run this Skill in your project directory. It automatically detects and removes unnecessary null-checks while supporting multiple programming languages.

You should not remove try/catch blocks from system boundary files like HTTP handlers and CLI entry points. This Skill automatically preserves these boundary catches and only targets defensive guards and error handling that lack a useful role.