Code Comments
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Install
npx skills add petekp/claude-code-setup --skill code-commentsgit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/code-comments ~/.claude/skills/code-commentsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code comments Delete every comment that is not on the keep list. When you are not sure a comment fits an item, delete it. A comment that explains our own code usually means the code should change: make the code say it, then delete the comment. Before adding a comment while writing code, hold it to the same list. ## Keep list A comment stays only when it is one of these, and only while its claim holds today: 1. **A legal or license header.** 2. **A tool directive**, such as `// prettier-ignore`, `@vitest-environment`, or a compiler pragma. Lint and type suppressions must also pass [Suppressions](#suppressions). 3. **A doc comment on an API used outside its module** that states what the signature and types cannot: units, ownership, side effects, errors thrown, rejected inputs. 4. **A constraint set outside our code**: a dependency or platform bug, a vendor or protocol rule, a business rule, a regulation. It names the source, and links the issue, spec, RFC, or ADR when one exists. A workaround also states the condition for removing it. 5. **A true constraint on our own code that the code cannot show yet**, such as a required call order, or a line that looks removable but is not. It stays only until a code change, type, assertion, or test removes the need (steps 2 and 4). 6. **A `TODO` that links a tracked issue.** ## Judge each comment Take each comment in scope through these steps in order.
Details
- Skill name
code-comments- Repository
- petekp/claude-code-setup
- Path
skills/code-comments/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the Code Comments skill do?
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
How do I install the Code Comments skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill code-comments. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Comments popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Catch Up
49petekp/claude-code-setup
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Deep Research
49petekp/claude-code-setup
Investigate a question that requires sustained research across sources and produce cited findings. Use for deep research requests; skip ordinary lookups and single-document reviews.
Exhaustive Systems Analysis
49petekp/claude-code-setup
Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.
Timovi Tech Lead
49theminimalcreator/timovi
Tech Lead for the Timovi project. Technical leadership for architecture, quality, planning, and execution with explicit trade-offs. Use when decomposing features into Issues, reviewing skill code, defining standards, or coordinating technical execution.
Latent Potential
49petekp/claude-code-setup
First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this become", "is there a bigger play here", "how do I make this valuable or impactful", "assess this project", "strategic review", "where should t
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.