clean-up-comments SKILL.md skillA
clean-up-comments from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/clean-up-comments@git:20261004.4b0ddb9Pins git:20261004.4b0ddb9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/clean-up-comments/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261004.4b0ddb9, committed Oct 4, 2026
- First version recorded
- May 29, 2026
- Size
- 1,739 bytes
- Repository stars
- 74,516
- License
- MIT
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.
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
# 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, …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/clean-up-comments@sha256:37ec4b0f7d87c9d8The line at the top of this page pins the label git:20261004.4b0ddb9, 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_hlcml6yi6jm6p3ox)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Oct 4, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.4b0ddb9 latest | 2026-10-04 | 4b0ddb9 | 1,739 B | A | view · diff |
| git:20260529.7c05904 | 2026-05-29 | 7c05904 | 1,745 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 (1739 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
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hlcml6yi6jm6p3ox GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/clean-up-comments GET https://markdownregistry.com/api/v1/blob/37ec4b0f7d87c9d8d6524c378a0e21847b86f46f235fec9a1b62e695eb105a60
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.