Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
A skill your agent uses when writing, fixing, editing, or reviewing TypeScript comments and TSDoc.
Install Clean Comments
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-comments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/typescript/clean-comments .claude/skills/clean-comments && rm -rf skills-srcUse ~/.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/
Install the "clean-comments" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-comments into .claude/skills/clean-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-comments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-commentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/typescript/clean-comments .agents/skills/clean-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clean-comments" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-comments into .agents/skills/clean-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-comments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/typescript/clean-comments .cursor/skills/clean-comments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clean-comments" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-comments into .cursor/skills/clean-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-comments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ertugrul-dmr/clean-code-skills.git --path skills/typescript/clean-comments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/typescript/clean-comments .gemini/skills/clean-comments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clean-comments" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-comments into .gemini/skills/clean-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-comments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ertugrul-dmr/clean-code-skills clean-commentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/typescript/clean-comments .github/skills/clean-comments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clean-comments" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-comments into .github/skills/clean-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-comments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/typescript/clean-comments .opencode/skills/clean-comments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clean-comments" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-comments into .opencode/skills/clean-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-comments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
clean-comments- GitHub stars
- 197
- Token cost
- ~428 tokens
- SKILL.md length
- 132 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing, fixing, editing, or reviewing TypeScript comments and TSDoc.
- Reviewing TypeScript comments and TSDoc
- SKILL.md covers C1: No Inappropriate Information, C2: Delete Obsolete Comments, C3: No Redundant Comments and C4: Write Comments Well, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Code quality
What it does
Clean Comments is an agent skill from ertugrul-dmr/clean-code-skills. Use when writing, fixing, editing, or reviewing TypeScript comments and TSDoc. Enforces Clean Code principles—no metadata, no redundancy, no commented-out code.
Its SKILL.md is about 430 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 Code quality. It works with TypeScript. The licence is MIT.
When your agent uses it
- Reviewing TypeScript comments and TSDoc
- Tasks that involve Code quality
Example prompts
- “/clean-comments”
What it can do on your machine
Read from SKILL.md and the folder at commit 1b6b3cc. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Clean Comments loads about 428 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 132 words of instructions outside code blocks.
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
The full file from ertugrul-dmr/clean-code-skills at commit 1b6b3cc, republished under its MIT licence (© ertugrul-dmr). 132 words, ~428 tokens.
Download SKILL.mdSave it as
.claude/skills/clean-comments/SKILL.md (or your agent's skills folder).- name
- clean-comments
- description
- Use when writing, fixing, editing, or reviewing TypeScript comments and TSDoc. Enforces Clean Code principles—no metadata, no redundancy, no commented-out code.
- when_to_use
- Also trigger on: commented-out code blocks, TODO/FIXME banners, author/ticket/date metadata in comments or TSDoc, TSDoc that no longer matches the code…
Clean Comments
C1: No Inappropriate Information
Comments shouldn't hold metadata. Use Git for author names, change history, ticket numbers, and dates. Comments are for technical notes about code only.
C2: Delete Obsolete Comments
If a comment describes code that no longer exists or works differently, delete it immediately. Stale comments become "floating islands of irrelevance and misdirection."
C3: No Redundant Comments
// Bad - the code already says this
i += 1; // increment i
user.save(); // save the user
// Good - explains WHY, not WHAT
i += 1; // compensate for zero-indexing in displayC4: Write Comments Well
If a comment is worth writing, write it well:
- Choose words carefully
- Use correct grammar
- Don't ramble or state the obvious
- Be brief
C5: Never Commit Commented-Out Code
// DELETE THIS - it's an abomination
// function oldCalculateTax(income: number): number {
// return income * 0.15;
// }Who knows how old it is? Who knows if it's meaningful? Delete it. Git remembers everything.
The Goal
The best comment is the code itself. If you need a comment to explain what code does, refactor first, comment last.
© ertugrul-dmr, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/typescript/clean-comments of ertugrul-dmr/clean-code-skills.
Open the folder on GitHubat commit 1b6b3cc
Compare with similar skills
Clean Comments 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clean Comments this skillertugrul-dmr/clean-code-skills | 197 | — | ~428 | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Code Reviewerjewbetcha/opentrace | 116 | 2 repos | ~1.1k | Automated safety check: Notes | MIT | |
| Coding Standardskurealnum/dotfiles | 290 | 17 repos | ~2.9k | Automated safety check: Pass | None | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Cross-Language Coding Standardszereight/gitlab-mcp | 2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Code Reviewer
jewbetcha/opentrace
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.
Coding Standards
kurealnum/dotfiles
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
Cross-Language Coding Standards
zereight/gitlab-mcp
Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.
DRY Refactoring With jscpd
kucherenko/jscpd
Removes copy-paste duplication found by jscpd, starting with exact clones and hotspots, then renamed and near-miss copies, using proven refactoring strategies.
More from ertugrul-dmr/clean-code-skills
All 14 skills in this repoBoy Scout
ertugrul-dmr/clean-code-skills
A skill your agent uses when fixing, editing, changing, debugging, or working with any Python code.
Boy Scout
ertugrul-dmr/clean-code-skills
A skill your agent uses when fixing, editing, changing, debugging, or working with any TypeScript code.
Clean General
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or reviewing Python code quality.
Clean General
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or reviewing TypeScript code quality.
Clean Names
ertugrul-dmr/clean-code-skills
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, or modules in Python.
Clean Names
ertugrul-dmr/clean-code-skills
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript.
Related
Works with
Categories
Questions about Clean Comments
What does Clean Comments do?
A skill your agent uses when writing, fixing, editing, or reviewing TypeScript comments and TSDoc. Clean Comments is an agent skill from ertugrul-dmr/clean-code-skills. Use when writing, fixing, editing, or reviewing TypeScript comments and TSDoc.
When should I use Clean Comments?
Clean Comments fits situations like: reviewing TypeScript comments and TSDoc; tasks that involve Code quality.
How do I install Clean Comments in Claude Code?
Run `npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a claude-code`. Or copy the skill folder (skills/typescript/clean-comments in ertugrul-dmr/clean-code-skills) into .claude/skills/clean-comments in your project. Claude Code loads it when a task matches its description.
How do I install Clean Comments in Codex?
Run `npx skills add ertugrul-dmr/clean-code-skills --skill clean-comments -a codex`. Or copy the skill folder (skills/typescript/clean-comments in ertugrul-dmr/clean-code-skills) into .agents/skills/clean-comments in your project. Codex loads it when a task matches its description.
Can I use Clean Comments 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 ertugrul-dmr/clean-code-skills --skill clean-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean-comments, .gemini/skills/clean-comments, .github/skills/clean-comments and .opencode/skills/clean-comments in your project.
What does Clean Comments need to run?
SKILL.md names no scripts, command-line tools or credentials: Clean Comments is instructions for the agent only.
Does Clean Comments access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Clean Comments 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 Clean Comments use?
Clean Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clean Comments use?
About 428 tokens (SKILL.md is roughly 1.7k 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 Clean Comments?
Skills that share tags, products or a category with Clean Comments: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Code Reviewer (jewbetcha/opentrace, 116 stars), Coding Standards (kurealnum/dotfiles, 290 stars) and Code Quality (redis/RedisInsight, 8.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clean Comments?
ertugrul-dmr (a GitHub user) maintains it in ertugrul-dmr/clean-code-skills, which has 197 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on April 21, 2026.
Source: ertugrul-dmr/clean-code-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.