← Back to Skills Marketplace
130
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install console-log-checker
Description
Checks specified directory for console.log statements, excluding common folders, and reports file locations and line previews of occurrences.
README (SKILL.md)
console-log-checker
Description
检查项目中是否存在 console.log 语句，帮助开发者清理调试代码。
When to Use
Use this skill when a user wants to:
- Check for forgotten console.log statements before commit/deploy
- Audit codebase for debugging statements
- Clean up leftover console.log calls
Inputs
-
path (string, optional) The directory path to check. Defaults to current working directory.
-
exclude (string, optional) Comma-separated glob patterns to exclude (e.g., "node_modules,dist,build").
Behavior
You are a code quality assistant.
When invoked:
- Use Grep tool to search for
console\.logpatterns in the codebase. - Exclude common directories like node_modules, dist, build by default.
- Report findings in a structured format.
Output Format
Return a summary with:
Console.log Check Results
| File | Line | Content Preview |
|---|---|---|
| path/to/file.js | 42 | console.log("debug...") |
Total found: X occurrences
Recommendations
- Suggest removing or replacing with proper logging
- Flag any in production-critical files
Usage Guidance
This skill is coherent and straightforward. Before running it, ensure you set the path argument to the repository or folder you want scanned (avoid pointing it at system or home directories). Provide appropriate exclude patterns (e.g., node_modules, build, .git) if you want to avoid scanning large or sensitive folders. Because it searches local files, run it only in environments where the agent is allowed to read the target files. If you need an extra safety step, run the equivalent grep locally or in a disposable clone of the repo before granting the agent access.
Capability Analysis
Type: OpenClaw Skill
Name: console-log-checker
Version: 1.0.0
The console-log-checker skill is a standard utility designed to help developers identify debugging statements in their codebase. It uses a grep tool to search for 'console.log' patterns and provides a structured report, with no evidence of malicious intent, data exfiltration, or suspicious instructions in SKILL.md or README.md.
Capability Assessment
Purpose & Capability
Name and description match the SKILL.md instructions: the skill's stated goal is to locate console.log statements and the instructions only require searching files under a given path. There are no unrelated environment variables, binaries, or install steps.
Instruction Scope
Runtime instructions tell the agent to use a Grep tool to search for `console\.log` and to exclude common directories by default. The instructions operate on local files under the provided path (defaults to CWD) and do not direct data to external endpoints or request unrelated system credentials. Note: because it reads files in the given path, avoid running it with a path that includes sensitive system or home directories.
Install Mechanism
No install spec is present and no code files are bundled. This is the lowest-risk model for an agent skill: nothing is written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportional to its function of searching a codebase for console.log occurrences.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modification of other skills' configs. Autonomous invocation is allowed by default but not unusual; nothing in the skill asks for elevated privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install console-log-checker - After installation, invoke the skill by name or use
/console-log-checker - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of console-log-checker.
- Checks project files for occurrences of console.log statements.
- Supports optional path and exclude parameters to customize the scan scope.
- Excludes common directories (node_modules, dist, build) by default.
- Returns results in a table with file, line, and code snippet preview.
- Provides recommendations for cleaning up or replacing debugging logs.
Metadata
Frequently Asked Questions
What is Console Log Checker?
Checks specified directory for console.log statements, excluding common folders, and reports file locations and line previews of occurrences. It is an AI Agent Skill for Claude Code / OpenClaw, with 130 downloads so far.
How do I install Console Log Checker?
Run "/install console-log-checker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Console Log Checker free?
Yes, Console Log Checker is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Console Log Checker support?
Console Log Checker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Console Log Checker?
It is built and maintained by Sy724 (@sy724); the current version is v1.0.0.
More Skills