Oxc
by ckchzh
Compile, bundle, and optimize JavaScript with high-performance build tools. Use when bundling modules, minifying builds, or analyzing bundle output sizes.
安装
claude skill add --url github.com/openclaw/skills/tree/main/skills/ckchzh/js-compiler文档
JS Compiler
JS Compiler v2.0.0 — a devtools toolkit for logging, tracking, and managing JavaScript compilation and build operations from the command line.
Each command accepts free-text input. When called without arguments it displays recent entries; when called with input it logs the entry with a timestamp for future reference.
Commands
| Command | Description |
|---|---|
js-compiler check <input> | Log a check entry (e.g. verify build output, check syntax) |
js-compiler validate <input> | Log a validation entry (e.g. validate config, confirm bundle integrity) |
js-compiler generate <input> | Log a generation entry (e.g. generate boilerplate, scaffold modules) |
js-compiler format <input> | Log a format entry (e.g. format source code, prettify output) |
js-compiler lint <input> | Log a lint entry (e.g. lint source files, check for code issues) |
js-compiler explain <input> | Log an explanation entry (e.g. explain build errors, annotate warnings) |
js-compiler convert <input> | Log a conversion entry (e.g. convert ESM→CJS, transform syntax) |
js-compiler template <input> | Log a template entry (e.g. save build config templates for reuse) |
js-compiler diff <input> | Log a diff entry (e.g. compare build outputs, highlight bundle changes) |
js-compiler preview <input> | Log a preview entry (e.g. preview build plan before execution) |
js-compiler fix <input> | Log a fix entry (e.g. fix compilation errors, resolve warnings) |
js-compiler report <input> | Log a report entry (e.g. summarize build results, bundle size report) |
Utility Commands
| Command | Description |
|---|---|
js-compiler stats | Show summary statistics across all entry types |
js-compiler export <fmt> | Export all data in json, csv, or txt format |
js-compiler search <term> | Search all entries for a keyword (case-insensitive) |
js-compiler recent | Show the 20 most recent activity log entries |
js-compiler status | Health check — version, data dir, entry count, disk usage |
js-compiler help | Show the built-in help message |
js-compiler version | Print version string (js-compiler v2.0.0) |
Data Storage
All data is stored locally in ~/.local/share/js-compiler/. Each command writes to its own log file (e.g. check.log, validate.log, lint.log). A unified history.log tracks all activity with timestamps. Exports are written to the same directory as export.json, export.csv, or export.txt.
Requirements
- Bash 4+ (uses
set -euo pipefail) - Standard Unix utilities:
date,wc,du,tail,grep,sed,cat - No external dependencies or network access required
When to Use
- Tracking build and compilation results — use
reportto log bundle sizes, build times, and success/failure status after each compilation, thensearchto find historical results. - Debugging compilation errors — use
explainto annotate error messages with root cause analysis,fixto log resolution steps, andcheckto verify the fix worked. - Comparing build outputs across versions — use
diffto log side-by-side comparisons of bundle sizes or build artifacts, thenexport csvto chart trends over time. - Managing build configuration templates — use
templateto save webpack/rollup/esbuild configs for different environments (dev, staging, prod), thensearchto find the right one quickly. - Linting and formatting JavaScript codebases — use
lintto log code quality issues found,formatto track formatting operations, andvalidateto confirm config files are correct before building.
Examples
# Log a build result
js-compiler report "Production build: 142KB gzipped, 0 errors, 3 warnings, 8.2s"
# Explain a compilation error
js-compiler explain "TypeError: Cannot read 'default' of undefined — circular import in utils/index.js"
# Fix a build issue
js-compiler fix "Resolved circular import by extracting shared types to types/common.ts"
# Compare two builds
js-compiler diff "v2.1: 138KB | v2.2: 155KB — 12% increase from new charting library"
# Save a build config template
js-compiler template "esbuild prod config: --bundle --minify --target=es2020 --splitting"
# Lint the codebase
js-compiler lint "ESLint run: 0 errors, 12 warnings (unused imports)"
# Search for all entries about bundle size
js-compiler search "bundle"
# View summary statistics
js-compiler stats
# Export all data to JSON
js-compiler export json
How It Works
JS Compiler is a lightweight Bash script that stores timestamped entries in plain-text log files. Each command follows the same pattern:
- No arguments → display the 20 most recent entries from that command's log
- With arguments → append a timestamped entry to the log and confirm the save
The stats command aggregates line counts across all .log files. The export command serializes all logs into your chosen format. The search command greps case-insensitively across every log file in the data directory.
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
相关 Skills
前端设计
by anthropics
面向组件、页面、海报和 Web 应用开发,按鲜明视觉方向生成可直接落地的前端代码与高质感 UI,适合做 landing page、Dashboard 或美化现有界面,避开千篇一律的 AI 审美。
✎ 想把页面做得既能上线又有设计感,就用前端设计:组件到整站都能产出,难得的是能避开千篇一律的 AI 味。
网页构建器
by anthropics
面向复杂 claude.ai HTML artifact 开发,快速初始化 React + Tailwind CSS + shadcn/ui 项目并打包为单文件 HTML,适合需要状态管理、路由或多组件交互的页面。
✎ 在 claude.ai 里做复杂网页 Artifact 很省心,多组件、状态和路由都能顺手搭起来,React、Tailwind 与 shadcn/ui 组合效率高、成品也更精致。
网页应用测试
by anthropics
用 Playwright 为本地 Web 应用编写自动化测试,支持启动开发服务器、校验前端交互、排查 UI 异常、抓取截图与浏览器日志,适合调试动态页面和回归验证。
✎ 借助 Playwright 一站式验证本地 Web 应用前端功能,调 UI 时还能同步查看日志和截图,定位问题更快。
相关 MCP 服务
GitHub
编辑精选by GitHub
GitHub 是 MCP 官方参考服务器,让 Claude 直接读写你的代码仓库和 Issues。
✎ 这个参考服务器解决了开发者想让 AI 安全访问 GitHub 数据的问题,适合需要自动化代码审查或 Issue 管理的团队。但注意它只是参考实现,生产环境得自己加固安全。
Context7 文档查询
编辑精选by Context7
Context7 是实时拉取最新文档和代码示例的智能助手,让你告别过时资料。
✎ 它能解决开发者查找文档时信息滞后的问题,特别适合快速上手新库或跟进更新。不过,依赖外部源可能导致偶尔的数据延迟,建议结合官方文档使用。
by tldraw
tldraw 是让 AI 助手直接在无限画布上绘图和协作的 MCP 服务器。
✎ 这解决了 AI 只能输出文本、无法视觉化协作的痛点——想象让 Claude 帮你画流程图或白板讨论。最适合需要快速原型设计或头脑风暴的开发者。不过,目前它只是个基础连接器,你得自己搭建画布应用才能发挥全部潜力。