인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
문서 및 사무 · SKILL.md

comment-analyzer

comment-analyzer

Reviews code comments for accuracy against actual implementation, detects comment rot, outdated documentation, and misleading inline comments. Use after refactoring, before PRs, or when comments might be stale.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: comment-analyzer description: Reviews code comments for accuracy against actual implementation, detects comment rot, outdated documentation, and misleading inline comments. Use after refactoring, before PRs, or when comments might be stale. allowed-tools: Read, Grep, Glob agent: comment-analyzer context: fork metadata: triggers: comment rot, stale comments, outdated docs, comment accuracy, misleading comments, review comments, JSDoc, JavaDoc, docstring related-skills: code-reviewer, documentation-generation domain: quality role: specialist scope: review output-format: report last-reviewed: "2026-03-16"

Iron Law: If the comment contradicts the code, the comment is wrong — never accept a comment at face value without reading the implementation it describes.

Comment Analyzer

Verifies that comments, docstrings, JSDoc, JavaDoc, and inline documentation accurately describe the actual code implementation.

When to Use

  • After refactoring code that has existing comments
  • Before opening a PR with documentation changes
  • When code was changed but comments might not have been updated
  • Code review gate for documentation accuracy

What to Check

CategoryDescription
AccuracyDoes the comment describe what the code actually does?
StalenessWas code changed but the comment not updated?
MisleadingDoes the comment describe different behavior than implemented?
CompletenessAre error cases, side effects undocumented?
RedundancyComments that just restate the code (i++ // increment i)

Severity Levels

LevelMeaning
CRITICALComment directly contradicts code behavior
HIGHComment describes old behavior after refactor
MEDIUMIncomplete — missing error cases, missing params
LOWRedundant or trivial comments

Output Format

## Comment Analysis: [scope]

### CRITICAL
- [file:line] Comment: "[quote]" -> Actual: [what code really does]

### HIGH
- [file:line] Comment: "[quote]" -> Stale since: [what changed]

### Summary
- Total: N (critical: X, high: Y, medium: Z, low: W)
- Recommendation: PASS / FAIL Comments need updates before PR
저장한 Skills