Agent skill

Comment Cleanup

by haacked in haacked/dotfiles

Delete and tighten code comments in source files after they are written.

No licenceAuto-check passedDevelopment

Install Comment Cleanup

skills CLI
$ npx skills add haacked/dotfiles --skill comment-cleanup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install haacked/dotfiles comment-cleanup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/haacked/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ai/skills/comment-cleanup .claude/skills/comment-cleanup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
comment-cleanup
GitHub stars
134
Token cost
~2.4k tokens
SKILL.md length
1,468 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
None found

At a glance

Delete and tighten code comments in source files after they are written.

  • Works in 6 steps: Collect the comments → Leave these alone → Hold doc comments to their own standard → …
  • The user says the comments are too wordy
  • SKILL.md covers Reading the Arguments and Steps
  • Calls git and bash

What it does

Comment Cleanup is an agent skill from haacked/dotfiles. Delete and tighten code comments in source files after they are written. Drops narration, restatement, and change-log comments, cuts the survivors to their essential facts, and rewrites the grammar of what remains. Use when the user says the comments are too wordy, asks to clean up or trim comments, or right after generating code that came out over-commented. Not for PR descriptions, review comments, or other prose; use plain-writing for those.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Technical documentation, Pull requests and Text to speech and voice. It works with Git. The repository describes itself as: My dotfiles and scripts I use on dev machines.

When your agent uses it

  • The user says the comments are too wordy
  • Asks to clean up
  • Right after generating code that came out over-commented

Example prompts

  • “/comment-cleanup”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Collect the comments
  2. Leave these alone
  3. Hold doc comments to their own standard
  4. Decide each inline comment
  5. Rewrite grammar in what survives
  6. Apply and report

What it can do on your machine

Read from SKILL.md and the folder at commit 23ffed9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Comment Cleanup loads about 2.4k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 1,468 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,468 words (~2,409 tokens).

“Authoring-time rules do not hold on their own; a model that just worked out a mechanism reliably over-explains it. This is the pass that runs afterward, over comments that already exist.”

— opening of SKILL.md by haacked
name
comment-cleanup
argument-hint
[<path>…] [--branch] [--parent <ref>] [--all] [--dry-run]
model
sonnet
metadata.execution-tier
balanced

Read the full SKILL.md on GitHub

Files

Just SKILL.md in ai/skills/comment-cleanup of haacked/dotfiles.

Open the folder on GitHubat commit 23ffed9

Compare with similar skills

Comment Cleanup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Comment Cleanup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Comment Cleanup this skillhaacked/dotfiles134—~2.4kAutomated safety check: PassNone
Sweep Commentsahmetb/dotfiles139—~2kAutomated safety check: PassApache-2.0
Ccsn No Commentskenryu42/cc-safety-net1.6k—~907Automated safety check: PassMIT
Prepare PR FilesQwenLM/qwen-code28k—~538Automated safety check: PassApache-2.0
Docs Updatergiuseppe-trisciuoglio/developer-kit355—~2.6kAutomated safety check: NotesMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Sweep Comments

    ahmetb/dotfiles

    Hold code comments and docstrings to a strict quality bar. An agent skill from ahmetb/dotfiles.

    139 GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Ccsn No Comments

    kenryu42/cc-safety-net

    Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there.

    1.6k GitHub stars~907 tokensUpdated today
    DevelopmentAuto-check passed
  • Prepare PR Files

    QwenLM/qwen-code

    Writes a PR title file and a template-filled PR body file from the current branch diff, without pushing, commenting or creating the pull request.

    28k GitHub stars~538 tokensUpdated today
    DevelopmentAuto-check passed
  • Docs Updater

    giuseppe-trisciuoglio/developer-kit

    Provides automated documentation updates by analyzing git changes between the current branch and the last release tag.

    355 GitHub stars~2.6k tokensUpdated 28 days ago
    DevelopmentAuto-check: notes
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

More from haacked/dotfiles

All 29 skills in this repo
  • Support

    haacked/dotfiles

    Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.

    134 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Analyze Permissions

    haacked/dotfiles

    Analyze accumulated permissions and suggest smart wildcard patterns.

    134 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Followup

    haacked/dotfiles

    Capture a follow-up item mid-session in seconds, list open items, close one, or run a review pass.

    134 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Handoff

    haacked/dotfiles

    Write or resume a handoff document so the next agent session can pick up the current work.

    134 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Note

    haacked/dotfiles

    Capture complex technical discoveries into structured, reusable notes.

    134 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Quarterly Planning

    haacked/dotfiles

    Draft quarterly goals for a PostHog team (defaults to Feature Flags), clustering open issues into themes and producing goals in PostHog's HOGS format.

    134 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Comment Cleanup

What does Comment Cleanup do?

Delete and tighten code comments in source files after they are written. Comment Cleanup is an agent skill from haacked/dotfiles. Delete and tighten code comments in source files after they are written.

When should I use Comment Cleanup?

Comment Cleanup fits situations like: the user says the comments are too wordy; asks to clean up; right after generating code that came out over-commented.

How do I install Comment Cleanup in Claude Code?

Run `npx skills add haacked/dotfiles --skill comment-cleanup -a claude-code`. Or copy the skill folder (ai/skills/comment-cleanup in haacked/dotfiles) into .claude/skills/comment-cleanup in your project. Claude Code loads it when a task matches its description.

How do I install Comment Cleanup in Codex?

Run `npx skills add haacked/dotfiles --skill comment-cleanup -a codex`. Or copy the skill folder (ai/skills/comment-cleanup in haacked/dotfiles) into .agents/skills/comment-cleanup in your project. Codex loads it when a task matches its description.

Can I use Comment Cleanup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add haacked/dotfiles --skill comment-cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/comment-cleanup, .gemini/skills/comment-cleanup, .github/skills/comment-cleanup and .opencode/skills/comment-cleanup in your project.

What does Comment Cleanup need to run?

Going by SKILL.md and its folder, Comment Cleanup needs the command-line tools its instructions call (git and bash). Our summary lists: Python 3.

Does Comment Cleanup access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Comment Cleanup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Comment Cleanup use?

No licence was found for Comment Cleanup or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Comment Cleanup use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Comment Cleanup?

Skills that share tags, products or a category with Comment Cleanup: Sweep Comments (ahmetb/dotfiles, 139 stars), Ccsn No Comments (kenryu42/cc-safety-net, 1.6k stars), Prepare PR Files (QwenLM/qwen-code, 28k stars) and Docs Updater (giuseppe-trisciuoglio/developer-kit, 355 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Comment Cleanup?

haacked (a GitHub user) maintains it in haacked/dotfiles, which has 134 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.

Source: haacked/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.