code-review-comment-analyzer

Analyze code comments for accuracy, completeness, and long-term maintainability.

21|8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/speednet-software/speedwave --skill code-review-comment-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-comment-analyzer
Source: https://github.com/speednet-software/speedwave/tree/main/.claude/skills/code-review-comment-analyzer
Command: npx skills add https://github.com/speednet-software/speedwave --skill code-review-comment-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code comments often become out-of-date or misleading, causing maintenance challenges and technical debt. This Skill ensures comments stay accurate, complete, and valuable over the lifecycle of a codebase.

Core Features & Use Cases

  • Factual Accuracy Checks: Verify that claims in comments align with actual code behavior, signatures, and edge cases.
  • Completeness Assessment: Identify missing context, preconditions, and potential side effects to prevent knowledge gaps.
  • Long-term Value Evaluation: Highlight comments likely to become stale and propose updates to preserve value.
  • Misleading Element Detection: Flag ambiguous or outdated wording and references to refactored code.
  • Improvement Recommendations: Provide actionable rewrites and additional context suggestions for maintainers.

Quick Start

Review the repository's comments and provide a prioritized set of edits to ensure accuracy and long-term maintainability.

Frequently Asked Questions about code-review-comment-analyzer

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

FAQPage Schema
How do I check code comments for factual accuracy during code reviews?

To check code comments for factual accuracy during code reviews, analyze the claims in the comments against actual code behavior, signatures, and edge cases to identify misleading or outdated wording.

What causes code comments to rot and create technical debt?

Code comments rot when they become out-of-date or misleading compared to the actual code behavior, creating technical debt and maintenance challenges that degrade long-term codebase maintainability.

How do I assess the completeness and long-term value of code documentation?

Assess the completeness of code documentation by identifying missing context, preconditions, and potential side effects, then highlight comments likely to become stale to preserve long-term value.

Can static analysis detect misleading or outdated wording in code comments?

Yes, static analysis can detect misleading or outdated wording in code comments by flagging ambiguous references to refactored code and evaluating comments against rigorous criteria like factual accuracy.

How do I generate actionable improvements for misleading code comments?

Generate actionable improvements for misleading code comments by analyzing the actual code behavior and providing prioritized rewrites and additional context suggestions to maintainers.