Global Commenting

Apply global commenting standards across multi-file codebases during editing and review.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/benjamindv36/checkpoint --skill global-commenting-benjamindv36
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Global Commenting
Source: https://github.com/benjamindv36/checkpoint/tree/main/.claude/skills/global-commenting
Command: npx skills add https://github.com/benjamindv36/checkpoint --skill global-commenting-benjamindv36

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the problem of outdated, redundant, or missing comments that make code harder to understand and maintain, leading to wasted time and potential errors.

Core Features & Use Cases

  • Self-Documenting Code: Prioritizes clear structure and naming to reduce the need for excessive comments.
  • Minimal, Helpful Comments: Guides the AI to add comments only for complex logic sections, ensuring they are evergreen.
  • Evergreen Information: Focuses on comments that remain relevant far into the future, avoiding temporary explanations.
  • Use Case: When reviewing a complex algorithm, automatically identify areas where self-documenting code can be improved or where a concise, evergreen comment would clarify non-obvious logic, reducing future maintenance effort.

Quick Start

Review the 'calculateTax' function and ensure all comments adhere to global commenting standards, focusing on clarity and evergreen information.

Frequently Asked Questions about Global Commenting

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

FAQPage Schema
How do I ensure comments are consistent across a multi-file codebase?

Global commenting standardizes comment placement and phrasing across modules and files. Apply commenting guidelines during code review to enforce repository-wide consistency, ensuring all comments follow the same conventions regardless of file type or language.

What makes a code comment evergreen and maintainable?

Evergreen comments explain non-obvious logic and design decisions that remain relevant long-term, avoiding temporary explanations tied to specific dates or versions. Focus comments on the 'why' behind complex sections rather than restating what the code does.

When should I add comments versus relying on self-documenting code?

Use self-documenting code—clear naming and structure—as your primary tool. Add minimal, targeted comments only for genuinely complex logic or non-obvious algorithms where code clarity alone cannot convey intent, reducing maintenance burden over time.

How do I identify which parts of code need comments during review?

During code review, flag complex algorithms, non-standard patterns, and sections where intent isn't apparent from structure and naming. Add concise, evergreen comments to clarify those areas while keeping the codebase lean and readable.

Can I apply global commenting standards to existing codebases with inconsistent comments?

Yes. Review and refactor existing comments to align with global standards, removing redundant or outdated ones and adding evergreen explanations where logic is complex. Standardize placement and phrasing across all modules to improve maintainability.