When to use this skill
- •When deciding whether code needs a comment
- •When writing self-documenting code through clear naming
- •When adding comments to explain complex business logic
- •When documenting non-obvious algorithms or decisions
- •When avoiding comments that describe what the code does (let code speak)
- •When removing outdated or misleading comments
- •When avoiding temporary comments about recent changes or fixes
- •When writing comments that will remain relevant over time
- •When documenting public APIs or interfaces
- •Applies to all source code files across the project
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