skills.rest
RaNDoM6913
RaNDoM6913COMMUNITY
Explore all skills by this author →
GitHub

comment-rot-analyzer

Analyze git history and code context to identify stale comments and outdated TODOs.

1|Updated Mar 23, 2026
Search Tags:#documentation#todo#static-analysis#quality-assurance#risk-management#analyze#code-comments
One-click install
npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill comment-rot-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment-rot-analyzer
Source: https://github.com/RaNDoM6913/claude-code-superkit/tree/main/packages/codex/skills/comment-rot-analyzer
Command: npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill comment-rot-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comments in code often become stale or misleading after refactors, causing confusion and missed maintenance opportunities. This Skill helps teams detect and quantify drift between code and the surrounding documentation, ensuring code understanding stays accurate as the project evolves.

Core Features & Use Cases

  • Detect stale TODOs, FIXME, and other markers that no longer reflect current behavior.
  • Flag comments that describe code behavior inaccurately or reference removed APIs.
  • Produce a structured report that highlights drift and proposes targeted fixes for code-quality health.

Quick Start

Run the analyzer on your repository to detect stale or misleading comments and TODOs.

Frequently Asked Questions about comment-rot-analyzer

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

FAQPage Schema
How do I detect stale code comments after refactoring?▼

You can identify outdated TODOs by running an analyzer on your codebase that verifies comment content against current code context and git history, producing a structured report of markers that no longer reflect behavior.

How does static analysis find outdated TODOs and FIXMEs?▼

Static analysis finds outdated TODOs and FIXMEs by applying code-context matching and comment-content verification against git history to flag markers that no longer reflect current behavior or reference removed APIs.

Can I use a comment drift analyzer on codebases with multiple files?▼

Yes, you can apply comment drift analysis to codebases with multiple files and recent refactors to systematically surface misleading documentation and quantify the drift between code and comments.

What is the best way to fix outdated comments that reference removed APIs?▼

The best way to fix outdated comments referencing removed APIs is to run an analyzer that proposes targeted fixes for code-quality health, using code-context matching to verify drift and generate a structured report.

When should I not use static analysis for comment verification?▼

You should avoid static analysis for comment verification when a repository lacks sufficient git history or recent refactors, as the analyzer requires this historical data to accurately verify code-context matching and detect drift.

Related Skills

Explore More Software Engineering Skills→
pedronauckpedronauck
567

lesson-learned

Analyzes git history to extract software engineering lessons and principles.

Community
Intermediate
EvolutionAPIEvolutionAPI
520

dev-ai-slop-cleaner

Detect AI-generated code bloat patterns and propose simplified replacements.

Official
Intermediate
RangeyRoverRangeyRover
3

speckit.checker

Run static analysis across multiple languages and generate prioritized issue reports.

Community
Intermediate
julianobarbosajulianobarbosa
7

reviewing-code

Review code for quality, bugs, security issues, and best practices using Codex.

Community
Advanced