code

Remove obvious and redundant comments from all files

Remove obvious and redundant comments from uncommitted changes

Add appropriate emoji to make content more engaging

Scan code generator files for string concatenation blocks missing @formatter:off guards or broken by auto-formatting. Fix violations using the code-generation skill.

Rewrite tests to use strict deep equality assertions

This agent should be invoked after making code changes and before running the build or committing. It removes redundant, obvious, or outdated comments while preserving important ones like TODOs and linter directives. <example> Context: The user has fixed a bug and the code contains old commented-out debugging code. user: "I've fixed the null pointer exception in the payment processor" assistant: "Good work fixing that bug. Now let me clean up the comments before we commit." <commentary> After bug fixes, there are often commented-out debug statements or old code. Use the comment-cleaner agent to clean these up. </commentary> assistant: "I'll run the comment-cleaner agent to remove any commented-out code and redundant comments" </example> <example> Context: The user has refactored code and there are comments describing old behavior. user: "I've refactored the data processing pipeline to use the new async pattern" assistant: "The refactoring looks complete. Let me clean up the comments next." <commentary> Refactoring often leaves behind comments about old implementations. Use the comment-cleaner agent to remove these outdated comments. </commentary> assistant: "I'll use the comment-cleaner agent to remove any comments that describe the old synchronous implementation" </example>

CLI guidelines. Use whenever using the Bash tool, which is almost always. Also use when you see "command not found: __zoxide_z" errors.

This skill should be used when the user asks to "fix formatter-off", "fix code generation formatting", "fix auto-formatted string concatenation", "add formatter off", or when writing, reviewing, or generating Java code generators that build source code via string concatenation. Also applies proactively when creating new code generation methods or modifying existing ones — always use @formatter:off guards and the one-output-line-per-source-line convention.

Code quality guidelines. ALWAYS use skill for ANY code changes.

Guidelines for comments in code. Use when adding, editing, or removing comments.