code-comments

Provide best practices for writing durable source comments.

1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielraffel/burl --skill code-comments-danielraffel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-comments
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/code-comments
Command: npx skills add https://github.com/danielraffel/burl --skill code-comments-danielraffel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides guidance on writing clear, lasting comments that improve code readability and maintainability.

Core Features & Use Cases

  • Comment Best Practices: Offers guidelines on when and what to comment to enhance code clarity.
  • Comment Rewrite Suggestions: Provides rewrite examples to convert non-durable comments into valuable ones.
  • Test Naming Standards: Recommends best practices for naming tests to ensure they are descriptive and clear.

Quick Start

Run the skill and follow the guidelines for writing comments in your codebase.

Frequently Asked Questions about code-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What makes source code comments durable and maintainable over time?

Best practices for code documentation recommend rewriting non-durable comments to explain code invariants, non-obvious decisions, and external constraints. This approach avoids process provenance and speculative future roadmaps.

How do I write code comments that explain non-obvious decisions?

To write valuable code comments, focus on explaining non-obvious decisions and external constraints rather than process provenance. This skill provides rewrite examples to convert non-durable comments into valuable ones.

When should I add comments to improve code maintainability?

You should add comments to improve code maintainability when the code involves invariants, non-obvious decisions, or external constraints. This skill offers guidelines on when and what to comment to enhance clarity.

What are the best practices for naming tests to ensure they are descriptive?

Best practices for naming tests recommend using descriptive and clear naming conventions. This skill provides specific standards to ensure test names clearly communicate their purpose and maintainability.

How do I rewrite non-durable comments into valuable source documentation?

Rewrite non-durable comments by removing process provenance and speculative roadmaps, focusing instead on code invariants and external constraints. The skill provides specific rewrite examples to convert comments into valuable documentation.