comment-supplement

Completes and corrects code comments without modifying any business logic or public contracts.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/lldwb/lldwb-claude-skills --skill comment-supplement-lldwb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comment-supplement
Source: https://github.com/lldwb/lldwb-claude-skills/tree/main/skills/comment-supplement
Command: npx skills add https://github.com/lldwb/lldwb-claude-skills --skill comment-supplement-lldwb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Codebases accumulate missing, inaccurate, or outdated comments that mislead maintainers, but fixing them by hand risks accidentally touching logic. This Skill provides a disciplined workflow that supplements and corrects comments while guaranteeing every change stays strictly inside comment blocks. ## Core Features & Use Cases - Three-category audit: Marks each location as missing, inaccurate, or outdated against a judgment checklist, with code as the sole source of truth. - Iron-clad safety rules: Never modifies business logic, signatures, annotations, default values, or enum values; ambiguous intent goes into a confirmation list for the user instead of being guessed. - Self-verification before commit: Uses git diff hunk-by-hunk review, git diff -w, and a compile/build check to prove all changes landed inside comments, then commits with a docs-type conventional message. - Use Case: Ask it to review a module's Java classes; it flags missing Javadoc, fixes parameter descriptions that no longer match implementations, lists uncertain items for your confirmation, and commits only comment changes. ## Quick Start Use the comment-supplement skill to fill in missing comments and fix outdated descriptions in the src/services directory.

Frequently Asked Questions about comment-supplement

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

FAQPage Schema
How do I fix outdated code comments without changing any logic?

Audit each comment against the actual implementation, marking items as missing, inaccurate, or outdated, then rewrite only the comment text. Verify with git diff that every changed hunk falls inside comment blocks and run a compile check before committing.

How to batch-update comments across many files or modules?

Split the work by directory or module and process one batch at a time, confirming uncertain items with the reviewer per batch. Read-only subagents can collect candidate locations in parallel, but the actual comment edits should be applied and verified centrally.

What should a good code comment actually say?

Good comments explain why the code exists and its constraints: preconditions, side effects, invariants, and edge cases. Avoid restating the code literally, TODO placeholders, or comments that duplicate information already obvious from signatures.

When should comment fixes not be handled as a comment-only change?

When comment problems coexist with logic, structural, or interface changes, handle everything together in a bug-fix workflow instead. Comment-only skills must never mix code edits into the same commit as comment changes.

How do I verify comment edits did not break the build?

Run git diff to confirm every hunk is inside a comment block, use git diff -w to isolate whitespace-only changes, then run the project's compile or build command. Any hunk outside comments or a failed build means revert that change before proceeding.