comment-cleanup SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
comment-cleanup from haacked/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add haacked/dotfiles/comment-cleanup@git:20260929.362fe34Pins git:20260929.362fe34 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- haacked/dotfiles
- Path
ai/skills/comment-cleanup/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260929.362fe34, committed Sep 29, 2026
- First version recorded
- Aug 27, 2026
- Size
- 9,638 bytes
- Repository stars
- 135
- License
- none declared
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Comment Cleanup 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. The standard is the rules below, which restate the Style section of `AGENTS.md` for a pass that runs after the fact. Read that section as well when the run has one, and hold to the rules below when it does not. The code shows how it works, so a comment earns its place only by carrying what the code cannot: a constraint, a deliberate deviation, a gotcha, a workaround. This skill enforces that by deleting, not by rewriting everything it finds. ## Reading the Arguments - With no arguments, the scope is the uncommitted work: the tracked-file diff (`git diff HEAD`, staged and unstaged both) plus every path `git ls-files --others --exclude-standard` reports. `git diff HEAD` never lists an untracked file, and a file created during this work has no hunk to scope to, so treat each one as an explicit path and put every comment in it in scope. That is the work just done, which is what the pipelines that call this skill mean by "the changes just made". …
Read the whole file at its exact version.
How to install
mdr add haacked/dotfiles/comment-cleanup@sha256:2352853b80636a72The line at the top of this page pins the label git:20260929.362fe34, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zjaye3ue54m3jijj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 27, 2026 and Sep 29, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260929.362fe34 latest | 2026-09-29 | 362fe34 | 9,638 B | A | view · diff |
| git:20260922.9dc6b96 | 2026-09-22 | 9dc6b96 | 9,559 B | A | view · diff |
| git:20260909.69436f2 | 2026-09-09 | 69436f2 | 9,407 B | A | view · diff |
| git:20260827.5b377ca | 2026-08-27 | 5b377ca | 8,484 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9638 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
haacked/dotfiles · 135 stars · license none declared · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zjaye3ue54m3jijj GET https://markdownregistry.com/api/v1/resolve?ref=haacked/dotfiles/comment-cleanup GET https://markdownregistry.com/api/v1/blob/2352853b80636a72b11223f8852a37abc2c7d3b68a9bd1d394dc83bd1c91b9a9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from haacked/dotfiles
Every file in haacked/dotfiles