/health
Comprehensive health check of a running Tauri application
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/health
Context preview
What this command does when you run it.
Comprehensive health check of a running Tauri application
Command definition
health.mdname: rust:tauri:health
description: Comprehensive health check of a running Tauri application
allowed-tools: mcp__tauri-mcp__get_app_logs, mcp__tauri-mcp__get_window_info, mcp__tauri-mcp__monitor_resources, mcp__tauri-mcp__list_ipc_handlers, mcp__tauri-mcp__execute_js
author: Quintin Henry (https://github.com/qdhenry/)
<objective> Perform a comprehensive health check on a running Tauri application, analyzing logs for errors, resource usage, window state, and IPC functionality. </objective>
<instructions> Health check the Tauri application: **$ARGUMENTS**
Arguments: `[process_id]`
Health Check Process
Perform ALL of the following checks:
1. Window Health
Use `mcp__tauri-mcp__get_window_info`:
- [ ] Window is visible
- [ ] Window has non-zero dimensions
- [ ] Window is not minimized (unless expected)
2. Resource Health
Use `mcp__tauri-mcp__monitor_resources`:
- [ ] CPU usage is reasonable (< 50% idle)
- [ ] Memory usage is acceptable
- [ ] No runaway resource consumption
3. Log Health
Use `mcp__tauri-mcp__get_app_logs`:
- [ ] No unhandled errors in recent logs
- [ ] No panic messages
- [ ] No critical warnings
4. IPC Health
Use `mcp__tauri-mcp__list_ipc_handlers`:
- [ ] IPC handlers are registered
- [ ] Expected commands are available
5. Frontend Health
Use `mcp__tauri-mcp__execute_js`:
- [ ] No JavaScript errors: `window.onerror === null`
- [ ] App is responsive: `document.readyState === 'complete'`
- [ ] Key elements exist: `!!document.querySelector('#root, #app, main')`
Usage Examples
# Run full health check
/tauri:health 12345
</instructions>
<output_format>
=== Tauri App Health Check ===
Process ID: [PID]
Timestamp: [time]
--- Window Health ---
[PASS] Window visible
[PASS] Dimensions: 1200x800
[PASS] Not minimized
--- Resource Health ---
[PASS] CPU: 5% (acceptable)
[PASS] Memory: 180 MB (acceptable)
--- Log Health ---
[PASS] No errors in last 100 lines
[WARN] 2 warnings detected (see details below)
--- IPC Health ---
[PASS] 24 commands registered
[PASS] Core commands available
--- Frontend Health ---
[PASS] Document ready
[PASS] No JS errors
[PASS] Root element exists
=== Overall Status: HEALTHY ===
(or DEGRADED / UNHEALTHY with details)
--- Warnings/Issues ---
[List any warnings or issues found]
--- Recommendations ---
[Suggested actions if any issues detected]
</output_format>
<severity_levels> **HEALTHY (Green):** All checks pass, no warnings.
**DEGRADED (Yellow):**
- Minor warnings in logs
- Slightly elevated resource usage
- Non-critical elements missing
**UNHEALTHY (Red):**
- Errors in logs
- Window not visible/responsive
- High resource usage
- IPC not functioning
- JavaScript errors
</severity_levels>
Read more
name: rust:tauri:health description: Comprehensive health check of a running Tauri application allowed-tools: mcp__tauri-mcp__get_app_logs, mcp__tauri-mcp__get_window_info, mcp__tauri-mcp__monitor_resources, mcp__tauri-mcp__list_ipc_handlers, mcp__tauri-mcp__execute_js author: Quintin Henry (https://github.com/qdhenry/)
<objective> Perform a comprehensive health check on a running Tauri application, analyzing logs for errors, resource usage, window state, and IPC functionality. </objective>
<instructions> Health check the Tauri application: **$ARGUMENTS**
Arguments: `[process_id]`
Health Check Process
Perform ALL of the following checks:
1. Window Health
Use `mcp__tauri-mcp__get_window_info`:
- [ ] Window is visible
- [ ] Window has non-zero dimensions
- [ ] Window is not minimized (unless expected)
2. Resource Health
Use `mcp__tauri-mcp__monitor_resources`:
- [ ] CPU usage is reasonable (< 50% idle)
- [ ] Memory usage is acceptable
- [ ] No runaway resource consumption
3. Log Health
Use `mcp__tauri-mcp__get_app_logs`:
- [ ] No unhandled errors in recent logs
- [ ] No panic messages
- [ ] No critical warnings
4. IPC Health
Use `mcp__tauri-mcp__list_ipc_handlers`:
- [ ] IPC handlers are registered
- [ ] Expected commands are available
5. Frontend Health
Use `mcp__tauri-mcp__execute_js`:
- [ ] No JavaScript errors: `window.onerror === null`
- [ ] App is responsive: `document.readyState === 'complete'`
- [ ] Key elements exist: `!!document.querySelector('#root, #app, main')`
Usage Examples
# Run full health check /tauri:health 12345
</instructions>
<output_format>
=== Tauri App Health Check === Process ID: [PID] Timestamp: [time] --- Window Health --- [PASS] Window visible [PASS] Dimensions: 1200x800 [PASS] Not minimized --- Resource Health --- [PASS] CPU: 5% (acceptable) [PASS] Memory: 180 MB (acceptable) --- Log Health --- [PASS] No errors in last 100 lines [WARN] 2 warnings detected (see details below) --- IPC Health --- [PASS] 24 commands registered [PASS] Core commands available --- Frontend Health --- [PASS] Document ready [PASS] No JS errors [PASS] Root element exists === Overall Status: HEALTHY === (or DEGRADED / UNHEALTHY with details) --- Warnings/Issues --- [List any warnings or issues found] --- Recommendations --- [Suggested actions if any issues detected]
</output_format>
<severity_levels> **HEALTHY (Green):** All checks pass, no warnings.
**DEGRADED (Yellow):**
- Minor warnings in logs
- Slightly elevated resource usage
- Non-critical elements missing
**UNHEALTHY (Red):**
- Errors in logs
- Window not visible/responsive
- High resource usage
- IPC not functioning
- JavaScript errors
</severity_levels>
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command

