No Comments
cursor/plugins
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production.
MITAuto-check passed
Install Clean Up Comments
$ npx skills add thedaviddias/Front-End-Checklist --skill clean-up-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist clean-up-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/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/clean-up-comments .claude/skills/clean-up-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-up-comments" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-comments into .claude/skills/clean-up-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up-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/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-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 thedaviddias/Front-End-Checklist --skill clean-up-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist clean-up-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/clean-up-comments .agents/skills/clean-up-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-up-comments" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-comments into .agents/skills/clean-up-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up-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 thedaviddias/Front-End-Checklist --skill clean-up-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist clean-up-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/clean-up-comments .cursor/skills/clean-up-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-up-comments" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-comments into .cursor/skills/clean-up-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up-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/thedaviddias/Front-End-Checklist.git --path skills/clean-up-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 thedaviddias/Front-End-Checklist --skill clean-up-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist clean-up-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/clean-up-comments .gemini/skills/clean-up-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-up-comments" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-comments into .gemini/skills/clean-up-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up-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 thedaviddias/Front-End-Checklist clean-up-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 thedaviddias/Front-End-Checklist --skill clean-up-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/clean-up-comments .github/skills/clean-up-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-up-comments" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-comments into .github/skills/clean-up-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up-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 thedaviddias/Front-End-Checklist --skill clean-up-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 thedaviddias/Front-End-Checklist clean-up-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/clean-up-comments .opencode/skills/clean-up-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-up-comments" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/clean-up-comments into .opencode/skills/clean-up-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up-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-up-comments- GitHub stars
- 74k
- Token cost
- ~435 tokens
- SKILL.md length
- 164 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production.
- Reviewing templates
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Shared components related to Remove comments and debug code in production
What it does
Clean Up Comments is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production. Validate the final browser-facing markup, not just the source framework abstraction.
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing templates
- Shared components related to Remove comments and debug code in production
Example prompts
- “/clean-up-comments”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. 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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
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 Up Comments loads about 435 tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 164 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 thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 164 words, ~435 tokens.
Download SKILL.mdSave it as
.claude/skills/clean-up-comments/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- clean-up-comments
- description
- Use when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production. Validate the final browser-facing markup, not just the source framework abstraction.
- metadata.category
- html
- metadata.priority
- medium
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/html/clean-up-comments
Remove comments and debug code in production
Comments expose internal logic to attackers, increase file size, and can leak sensitive information like API endpoints, credentials, or system architecture.
Quick Reference
- Remove TODO, FIXME, DEBUG comments before production
- Keep accessibility and legal comments
- Configure build tools to strip comments automatically
- Review for sensitive data leaks in comments
Check
Review this HTML code for unnecessary comments, debug code, console logs, and temporary markup that should be removed before production deployment.
Fix
Remove all development comments, debug code, unused markup, and temporary elements from the HTML before deploying to production.
Explain
Explain why cleaning up code before production is important for security, performance, and professional presentation of web applications.
Code Review
Review templates, server-rendered HTML, and shared components that output markup related to Remove comments and debug code in production. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/html/clean-up-comments
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/clean-up-comments of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Clean Up 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 Up Comments this skillthedaviddias/Front-End-Checklist | 74k | — | ~435 | Automated safety check: Pass | MIT | |
| No Commentscursor/plugins | 11k | 7 repos | ~640 | Automated safety check: Pass | None | |
| Commentsanthropics/claude-for-legal | 9.6k | 1 repos | ~1k | Automated safety check: Pass | Apache-2.0 | |
| RenderLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Android Clean Architectureaffaan-m/ECC | 276k | 4 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Comment Checkercode-yeongyu/oh-my-openagent | 70k | — | ~160 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
- Official
Comments
anthropics/claude-for-legal
Review open NPRM comment periods, log decisions, track deadlines.
Render
LeoYeAI/openclaw-master-skills
Deploy and operate apps on Render (Blueprint + one-click Dashboard deeplink, same flow as Codex render-deploy).
Android Clean Architecture
affaan-m/ECC
Applies Clean Architecture to Android and Kotlin Multiplatform projects: module layout, dependency rules, UseCases, Repositories and data layer patterns.
Comment Checker
code-yeongyu/oh-my-openagent
A skill your agent uses when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
- Official
Writing Comments
withastro/astro
How to write JSDoc (/ /) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Questions about Clean Up Comments
What does Clean Up Comments do?
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production. Clean Up Comments is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production.
When should I use Clean Up Comments?
Clean Up Comments fits situations like: reviewing templates; shared components related to Remove comments and debug code in production.
How do I install Clean Up Comments in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill clean-up-comments -a claude-code`. Or copy the skill folder (skills/clean-up-comments in thedaviddias/Front-End-Checklist) into .claude/skills/clean-up-comments in your project. Claude Code loads it when a task matches its description.
How do I install Clean Up Comments in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill clean-up-comments -a codex`. Or copy the skill folder (skills/clean-up-comments in thedaviddias/Front-End-Checklist) into .agents/skills/clean-up-comments in your project. Codex loads it when a task matches its description.
Can I use Clean Up 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 thedaviddias/Front-End-Checklist --skill clean-up-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-up-comments, .gemini/skills/clean-up-comments, .github/skills/clean-up-comments and .opencode/skills/clean-up-comments in your project.
What does Clean Up Comments need to run?
SKILL.md names no scripts, command-line tools or credentials: Clean Up Comments is instructions for the agent only.
Does Clean Up Comments access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Clean Up 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 Up Comments use?
Clean Up 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 Up Comments use?
About 435 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. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Clean Up Comments?
Skills that share tags, products or a category with Clean Up Comments: No Comments (cursor/plugins, 11k stars), Comments (anthropics/claude-for-legal, 9.6k stars), Render (LeoYeAI/openclaw-master-skills, 2.2k stars) and Android Clean Architecture (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clean Up Comments?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.