comment-analyzer

Analyze code comments for factual accuracy, completeness, and maintainability.

4|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/euxx/claude-skills-for-copilot --skill comment-analyzer-euxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comment-analyzer
Source: https://github.com/euxx/claude-skills-for-copilot/tree/main/skills/comment-analyzer
Command: npx skills add https://github.com/euxx/claude-skills-for-copilot --skill comment-analyzer-euxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams detect inaccurate, incomplete, or outdated code comments before they become a source of confusion and maintenance risk.

Core Features & Use Cases

  • Factual Verification: Checks whether comments match actual function signatures, behavior, types, and edge-case handling.
  • Maintainability Review: Flags comments that merely restate obvious code or are likely to age poorly.
  • Misleading Documentation Detection: Surfaces ambiguous, outdated, or contradictory guidance in docstrings and inline notes.
  • Use Case: A reviewer can run this Skill after a refactor to find docstrings that still describe old behavior or assumptions.

Quick Start

Ask the comment analyzer skill to review the specified file or directory for inaccurate, missing, or low-value comments.

Frequently Asked Questions about comment-analyzer

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

FAQPage Schema
How do I detect outdated or misleading code comments after a refactor?

To detect outdated code comments after a refactor, cross-check comment claims against actual function behavior and signatures. This analysis surfaces misleading documentation and outdated references to prevent comment rot and maintenance risks.

What is comment rot and how do I identify low-value comments in my codebase?

Comment rot occurs when documentation becomes inaccurate or outdated as code changes. Identify low-value comments by analyzing docstrings and inline notes for obvious restatements of code, ambiguity, or contradictory guidance that will age poorly over time.

How do I audit docstrings for factual accuracy across a directory?

Audit docstrings across a directory by analyzing them for factual accuracy, completeness, and maintainability. Cross-check documentation claims against actual code behavior, types, and edge-case handling to produce structured findings with issues and suggestions.

Can I use an automated code review to flag comments that restate obvious code?

Yes, you can flag comments that restate obvious code by running a maintainability review on your files. This analysis identifies low-value restatements and ambiguous documentation, producing structured findings with suggested removals and positives.

What is the best way to verify edge-case handling matches its docstring documentation?

The best way to verify edge-case handling matches docstrings is to cross-check comment claims against actual code behavior and types. This factual verification identifies contradictions and missing assumptions in your inline notes and docstrings.

Why do my code reviews miss contradictory guidance in inline notes?

Code reviews often miss contradictory guidance in inline notes because manual checks fail to systematically cross-check comment claims against actual code behavior. Automating this analysis surfaces ambiguous, outdated, or contradictory documentation effectively.