Why Did You Render
render-debugger by Welldone Software monkey patches React to notify you about potentially avoidab why did you render, javascript, component, hooks-tracking.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bytesagain/render-debuggerRender Debugger
Developer tools CLI for checking, validating, generating, and debugging render performance issues. Lint components for unnecessary re-renders, explain render behavior, convert between profiling formats, generate optimization templates, diff render snapshots, preview component trees, fix render issues, and produce performance reports — all from the command line with persistent local logging.
Commands
Run render-debugger <command> [args] to use.
| Command | Description |
|---|---|
check | Check components for render performance issues |
validate | Validate render optimization patterns and memo usage |
generate | Generate render-optimized component boilerplate |
format | Format render profiling data for readability |
lint | Lint components for unnecessary re-renders and anti-patterns |
explain | Explain why a component re-rendered and suggest fixes |
convert | Convert between render profiling data formats |
template | Apply or manage render optimization templates |
diff | Diff render snapshots to identify regression |
preview | Preview component render tree and dependency graph |
fix | Auto-fix common render performance issues |
report | Generate render performance and optimization reports |
stats | Show summary statistics across all categories |
export <fmt> | Export data in json, csv, or txt format |
search <term> | Search across all logged entries |
recent | Show recent activity from history log |
status | Health check — version, data dir, disk usage |
help | Show help and available commands |
version | Show version (v2.0.0) |
Each domain command (check, validate, generate, etc.) works in two modes:
- Without arguments: displays the most recent 20 entries from that category
- With arguments: logs the input with a timestamp and saves to the category log file
Data Storage
All data is stored locally in ~/.local/share/render-debugger/:
- Each command creates its own log file (e.g.,
check.log,validate.log,lint.log) - A unified
history.logtracks all activity across commands - Entries are stored in
timestamp|valuepipe-delimited format - Export supports JSON, CSV, and plain text formats
Requirements
- Bash 4+ with
set -euo pipefailstrict mode - Standard Unix utilities:
date,wc,du,tail,grep,sed,cat - No external dependencies or API keys required
When to Use
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bytesagain-render-debugger": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
workflow-builder
工作流设计与优化工具。流程设计、自动化方案、流程优化、文档化、审批流、系统集成。Workflow builder with design, automate, optimize, document, approval.
wp-manager
Manage WordPress sites from terminal. Use when checking site health, listing posts and pages, searching content, or running security scans.
volume
Volume reference tool. Use when working with volume in finance contexts.
xhs-content-creator
Generate viral Xiaohongshu notes with titles, tags, and covers. Use when drafting seed posts, writing reviews, crafting tutorials, or boosting engagement.
Webhook Tester
Send test payloads and inspect webhook responses locally. Use when debugging integrations, validating schemas, testing error handling, or simulating calls.