When to use this skill:
- •When deciding whether to add a comment to code
- •When writing comments for complex logic or algorithms
- •When commenting large sections of business logic
- •When tempted to write a comment about a recent change or fix
- •When considering adding TODO or FIXME comments
- •When the code could be made self-documenting through better naming
- •When reviewing existing comments for accuracy
- •When removing outdated or misleading comments
- •When ensuring comments are evergreen and future-relevant
- •When documenting why code exists, not what it does
- •When working on any file that may need explanatory comments
Global Commenting
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global commenting.
Instructions
For details, refer to the information provided in this file: global commenting