code-comment-standard

Enforce Java Javadoc and inline comment standards across classes, methods, and fields.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/codernai14-source/Forgex --skill code-comment-standard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-comment-standard
Source: https://github.com/codernai14-source/Forgex/tree/main/.cursor/skills/code-comment-standard
Command: npx skills add https://github.com/codernai14-source/Forgex --skill code-comment-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Java codebases often suffer from inconsistent, unreadable comments that hinder maintenance and onboarding. This skill provides a comprehensive guideline for writing clear, consistent comments across classes, methods, and fields in Java, following Javadoc conventions and team standards.

Core Features & Use Cases

  • Class-level, method-level, and field-level comment templates and examples
  • Standardized comment types (file, class, method, field, and inline comments) and their formats
  • Practical examples and notes on maintaining synchronized comments during refactors

Quick Start

Write Java classes with Javadoc-style class and method comments, and document fields to ensure clarity and maintainability.

Frequently Asked Questions about code-comment-standard

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

FAQPage Schema
How do I enforce consistent Java code comments across my project?

To enforce consistent Java code comments, apply standardized templates for class, method, and field levels using Javadoc conventions. This ensures readability and maintainability across the entire project by targeting specific documentation levels with structured guidance and exemplars.

What is the best way to format Javadoc for methods and classes?

The best way to format Javadoc is using standardized templates for class-level, method-level, and field-level documentation. It includes practical examples and conventions for inline notes, TODO, and WARNING comments to maintain code clarity.

How do I keep Java documentation synchronized during code refactors?

Keep Java documentation synchronized during code refactors by following practical examples and notes on maintaining consistent comments. Updated Javadoc must reflect refactored logic to ensure class and method documentation remains fully aligned.

When should I use inline comments versus Javadoc in Java?

Use Javadoc for class-level, method-level, and field-level documentation to provide structured API clarity, whereas use inline comments for specific TODO, NOTE, or WARNING conventions inside the code logic to ensure maintainability.

Does this Java commenting standard require any specific configuration files?

Yes, this Java commenting standard requires a YAML frontmatter name and description in the SKILL.md file. This configuration defines the standardized comment types and formats applied across the Java project to enforce documentation rules.