skills.rest
kubrickcode
kubrickcodeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

comment-review

Review code comments and remove unnecessary ones while preserving legitimate documentation.

1|Updated Mar 8, 2026
Search Tags:#code quality#git#code review#refactoring#technical debt#comments#code cleanup
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --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/cine-mirror/tree/main/.agents/skills/comment-review
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill comment-review-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate comment debt: outdated explanations, obvious narrations, and commented-out code that mislead developers and increase maintenance cost. This Skill aggressively audits comments and enforces a strict keep-or-delete policy. ## Core Features & Use Cases - Aggressive Comment Classification: Sorts every comment into REMOVE, IMPROVE, or KEEP based on seven strict legitimate categories (public API docs, business WHY, external constraints, and more). - Git-Aware Targeting: Automatically scopes the review to uncommitted changes, the latest commit, or the full project based on your input. - Multi-Language Support: Recognizes comment syntax for TypeScript, JavaScript, Go, Python, HTML, and JSX. - Use Case: Before merging a pull request, run the review on your uncommitted changes to strip redundant comments and get refactoring suggestions (like renaming functions) so the code explains itself. ## Quick Start Review the comments in my uncommitted changes and remove any that are unnecessary.

Frequently Asked Questions about comment-review

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

FAQPage Schema
How do I remove unnecessary comments from my code?▼

Run the comment review on your changed files or entire project. It classifies each comment as REMOVE, IMPROVE, or KEEP, deletes obvious narrations and commented-out code, and suggests refactors like better function names to replace explanatory comments.

What types of code comments should be kept?▼

Keep only public API documentation, business-logic WHY explanations, external dependency constraints, performance or security warnings, genuinely cryptic patterns, legal headers, and TODOs with an owner and ticket. Everything else is removed or refactored.

Which programming languages does comment review support?▼

It recognizes comment syntax for TypeScript, JavaScript, Go, Python, HTML, and JSX, including line comments, block comments, docstrings, and JSX comment braces.

Can I review comments only in uncommitted changes?▼

Yes. With no arguments, the review checks git status and analyzes uncommitted changes via git diff. If the working tree is clean, it falls back to reviewing the latest commit, and only scans the full project when explicitly requested.

When should I not delete a code comment?▼

Keep a comment when it explains WHY rather than WHAT, cannot be expressed through clearer code, matches a legitimate category like legal or external API constraints, and is verified accurate and concise.

Related Skills

Explore More Software Engineering Skills→
cncorpcncorp

git-writer

Remove tracked files with git rm while preserving uncommitted changes.

Official
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

refactoring

Refactor code incrementally with tests and isolated commits.

Official
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
dallascrilleydallascrilley

Commenting Intent

Guides writing code comments that explain intent and decisions rather than restating mechanics.

Community
Basic