comment-review

Review code comments and identify unnecessary annotations for removal.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill aggressively identifies and removes unnecessary comments, enforcing the principle that code should be self-explanatory and comments represent technical debt.

Core Features & Use Cases

  • Comment Auditing: Analyzes code to find comments that violate strict criteria for legitimacy.
  • Automated Cleanup: Identifies comments for deletion or suggests refactoring for those that need improvement.
  • Use Case: A developer wants to quickly reduce the comment clutter in a legacy codebase before a major refactor, ensuring only essential, high-value comments remain.

Quick Start

Use the comment-review skill to analyze the latest commit for unnecessary comments.

Frequently Asked Questions about comment-review

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

FAQPage Schema
How do I clean up unnecessary code comments that explain what the code does?

To clean up unnecessary code comments, you can audit your codebase to identify and remove annotations that merely explain what the code does. This enforces a strict policy where code should be self-explanatory, treating redundant comments as technical debt to improve maintainability.

What is the best way to review code comments in a legacy codebase before refactoring?

The best way to review code comments in a legacy codebase is to perform an aggressive comment audit that identifies outdated or unnecessary annotations. This process enforces code clarity by suggesting the deletion of low-value comments and the refactoring of those needing improvement.

How do I identify and remove technical debt caused by outdated code annotations?

You identify and remove technical debt from outdated code annotations by running a comment review that enforces strict legitimacy criteria. It flags comments explaining what code does for deletion and suggests refactoring for annotations that need improvement.

When should I remove comments that explain what my code does?

You should remove comments that explain what your code does when the code is already self-explanatory. Enforcing a strict comment policy treats these explanatory annotations as technical debt, prioritizing code clarity and long-term maintainability over redundant documentation.

Does comment review work with specific git targets or user-specified files?

Yes, comment review works with specific git targets or user-specified files. The analysis can be configured to review code based on user-specified targets, current git status, or the latest commit history to find unnecessary annotations.