Cleanup
simstudioai/sim
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Remove console statements in production.
MITAuto-check passed
Install Console Cleanup
$ npx skills add thedaviddias/Front-End-Checklist --skill console-cleanup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist console-cleanup --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/console-cleanup .claude/skills/console-cleanup && 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 "console-cleanup" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/console-cleanup into .claude/skills/console-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "console-cleanup", 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/console-cleanupType 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 console-cleanup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist console-cleanup --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/console-cleanup .agents/skills/console-cleanup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "console-cleanup" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/console-cleanup into .agents/skills/console-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "console-cleanup", 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 console-cleanup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist console-cleanup --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/console-cleanup .cursor/skills/console-cleanup && 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 "console-cleanup" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/console-cleanup into .cursor/skills/console-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "console-cleanup", 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/console-cleanup--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 console-cleanup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist console-cleanup --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/console-cleanup .gemini/skills/console-cleanup && 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 "console-cleanup" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/console-cleanup into .gemini/skills/console-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "console-cleanup", 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 console-cleanupInstalls 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 console-cleanup -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/console-cleanup .github/skills/console-cleanup && 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 "console-cleanup" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/console-cleanup into .github/skills/console-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "console-cleanup", 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 console-cleanup -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 console-cleanup --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/console-cleanup .opencode/skills/console-cleanup && 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 "console-cleanup" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/console-cleanup into .opencode/skills/console-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "console-cleanup", 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
console-cleanup- GitHub stars
- 74k
- Token cost
- ~452 tokens
- SKILL.md length
- 159 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 scripts, client components, bundles, or runtime behavior related to Remove console statements in production.
- Reviewing scripts
- 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
- Client components
What it does
Console Cleanup is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing scripts, client components, bundles, or runtime behavior related to Remove console statements in production. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Its SKILL.md is about 450 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 scripts
- Client components
- Runtime behavior related to Remove console statements in production
Example prompts
- “/console-cleanup”
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
Console Cleanup loads about 452 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 159 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). 159 words, ~452 tokens.
Download SKILL.mdSave it as
.claude/skills/console-cleanup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- console-cleanup
- description
- Use when reviewing scripts, client components, bundles, or runtime behavior related to Remove console statements in production. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
- metadata.category
- javascript
- metadata.priority
- medium
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/javascript/console-cleanup
Remove console statements in production
Console statements leak sensitive information, impact performance, and create unprofessional user experiences when visible in production.
Quick Reference
- Remove console.log, console.debug, console.table before production
- Use environment-aware logging utilities
- Configure build tools to strip console statements automatically
- Keep console.error for critical error tracking if needed
Check
Scan this JavaScript code for console.log, console.debug, console.warn, console.error, and other console statements that should be removed before production deployment.
Fix
Remove or conditionally disable console statements for production, or replace them with a proper logging service.
Explain
Explain why console statements should be removed from production code and alternatives for logging.
Code Review
Review scripts, client components, and browser execution paths related to Remove console statements in production. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/javascript/console-cleanup
© 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/console-cleanup of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Console Cleanup 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 |
|---|---|---|---|---|---|---|
| Console Cleanup this skillthedaviddias/Front-End-Checklist | 74k | — | ~452 | Automated safety check: Pass | MIT | |
| Cleanupsimstudioai/sim | 30k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Triage Support Bundlenetdata/netdata | 81k | — | ~2.7k | Automated safety check: Pass | GPL-3.0 | |
| Ssma Consolegithub/awesome-copilot | 40k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Git Worktree Cleanuplobehub/lobehub | 83k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Vibe Code Cleanupsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.8k | Automated safety check: Notes | MIT |
Similar skills
Triage Support Bundle
netdata/netdata
Investigate a Netdata support bundle offline - the archive netdata-support-bundle produces - to explain one host's alerts, missing data, collector failures, crashes, high CPU or memory, streaming…
- Official
Ssma Console
github/awesome-copilot
A skill your agent uses when: SSMA console operations — create project, generate assessment report, convert schema, migrate data, Oracle to SQL Server migration, schema conversion, data migration
Git Worktree Cleanup
lobehub/lobehub
Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.
Vibe Code Cleanup
sickn33/agentic-awesome-skills
Safe production cleanup and hardening for vibe-coded fullstack apps (Next.js, React, Node.js, etc.).
Cleanup
trycompai/comp
MUST run after writing or modifying code — reviews changed files for verbose patterns, inconsistencies, and readability issues before considering work done
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 Console Cleanup
What does Console Cleanup do?
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Remove console statements in production. Console Cleanup is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing scripts, client components, bundles, or runtime behavior related to Remove console statements in production.
When should I use Console Cleanup?
Console Cleanup fits situations like: reviewing scripts; client components; runtime behavior related to Remove console statements in production.
How do I install Console Cleanup in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill console-cleanup -a claude-code`. Or copy the skill folder (skills/console-cleanup in thedaviddias/Front-End-Checklist) into .claude/skills/console-cleanup in your project. Claude Code loads it when a task matches its description.
How do I install Console Cleanup in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill console-cleanup -a codex`. Or copy the skill folder (skills/console-cleanup in thedaviddias/Front-End-Checklist) into .agents/skills/console-cleanup in your project. Codex loads it when a task matches its description.
Can I use Console Cleanup 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 console-cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/console-cleanup, .gemini/skills/console-cleanup, .github/skills/console-cleanup and .opencode/skills/console-cleanup in your project.
What does Console Cleanup need to run?
SKILL.md names no scripts, command-line tools or credentials: Console Cleanup is instructions for the agent only.
Does Console Cleanup 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 Console Cleanup 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 Console Cleanup use?
Console Cleanup 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 Console Cleanup use?
About 452 tokens (SKILL.md is roughly 1.8k 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 804 tokens, read only when the agent opens those files.
What are the alternatives to Console Cleanup?
Skills that share tags, products or a category with Console Cleanup: Cleanup (simstudioai/sim, 30k stars), Triage Support Bundle (netdata/netdata, 81k stars), Ssma Console (github/awesome-copilot, 40k stars) and Git Worktree Cleanup (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Console Cleanup?
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.