← ClaudeAtlas

review-commentslisted

Review and clean up code comments for necessity, accuracy, non-duplication, clarity, and concise explanation of rationale. Use when comments may restate code, repeat a "why" already explained in the file, contain stale or vague claims, or need tightening before a PR.
nielsmadan/skills · ★ 0 · Code & Development · score 75
Install: claude install-skill nielsmadan/skills
<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Review Comments Review each comment in its full-file context, then offer actionable removals, rewrites, or code refactors. ## Flags - `--staged` - git staged files - `--unpushed` - files changed across all unpushed commits - `--changed` - git unstaged changes - `--all` - entire codebase (parallel agents) - `--fix` - apply safe comment-only removals and rewrites without prompting - `targets` - one or more source files or directories; overrides scope flags - Default: `--staged --changed` combined ## Usage ``` /review-comments # staged + changed (default) /review-comments --all # entire codebase /review-comments --fix # review and auto-fix /review-comments src/auth # review a file or directory ``` ## Gotchas - Framework directives (`// @ts-ignore`, `// eslint-disable`, `// noinspection`) look like "what" comments but are functional. Removing them silently breaks linting or type checking. - `--staged` on a clean working tree (everything already committed) reviews nothing and reports "No files to review" — which looks like a passing review. Use `--all` after committing. - Scope flags select files, not only changed lines. Read each selected file in full so repeated rationale and stale explanations can be detected. ## Workflow ### Step 1: Parse Flags From `$ARGUMENTS`, determine scope: | Flags Present | Scope | |---------------|-------| | (no