Analyze source code to remove unnecessary comments and enforce TODO ownership.
npx skills add https://github.com/specvital/infra --skill comment-review-specvital
Please help me install this Agent Skill. Skill: comment-review Source: https://github.com/specvital/infra/tree/main/.claude/skills/comment-review Command: npx skills add https://github.com/specvital/infra --skill comment-review-specvital
This Skill aggressively reduces comment debt by identifying and removing unnecessary comments, outdated notes, and misleading narrations that do not add value to the codebase.
Run the comment-review skill on a file or directory to analyze and delete non-essential comments, then review the generated report and apply recommended refactors.
High-intent search queries and answers about installing and using this skill.
To clean up unnecessary code comments, you can analyze source files to aggressively detect and remove verbose or outdated notes. This process enforces refactoring over comment-based explanations, producing a cleaner, self-explanatory codebase ready for maintainability.
The best way to handle TODO comments missing owners and tickets is to enforce a strict review rule that requires this metadata. Analyzing the codebase identifies non-compliant TODOs and guides developers to either add the required tracking information or remove the debt through refactoring.
Yes, you can use static analysis to remove code comments across an entire project. The analysis applies to single files or entire directories across multiple languages, targeting legacy code with comment debt to suggest deletions and refactors for non-essential narrations.
Yes, aggressive comment cleanup preserves explanations for complex logic by applying context-aware pruning. It retains essential comments that explain external rules or the WHY principle behind difficult code, while identifying and removing misleading narrations that do not add value.
You should avoid removing comments during code refactoring when the comment explains external rules or complex logic using the WHY principle. Legitimate explanations that clarify non-obvious constraints are intentionally preserved, while redundant or outdated notes are safely pruned.
uukuguyCalculate complexity, size, coupling, and duplication metrics from source code.
DieStokSimplify changed source code while preserving behavior and passing tests.
cpfcoachingTeach structured git workflows including trunk-based development and atomic commits.
skylarsaboStandardizes code style and formatting using tools like Prettier and ESLint.
