# Clean Up Comments

> 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.

- Skill: `thedaviddias/clean-up-comments` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add thedaviddias/clean-up-comments`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedaviddias/clean-up-comments/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: thedaviddias (https://skillmd.com/u/thedaviddias)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thedaviddias/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/en/rules/html/clean-up-comments