skills.rest
Botool-Dev-Team
Botool-Dev-TeamOFFICIAL
Explore all skills by this author →
GitHub

botoolagent-ide-debug

Diagnose IDE health issues by prioritizing fatal errors first.

Updated Aug 27, 2026
Search Tags:#debugging#frontend#mcp#devtools#diagnostics#ide#web-application
One-click install
npx skills add https://github.com/Botool-Dev-Team/BotoolAgent --skill botoolagent-ide-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: botoolagent-ide-debug
Source: https://github.com/Botool-Dev-Team/BotoolAgent/tree/main/skills/BotoolAgent/IDE-Debug
Command: npx skills add https://github.com/Botool-Dev-Team/BotoolAgent --skill botoolagent-ide-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies IDE health issues and prioritizes fatal errors to reduce debugging time, ensuring critical problems are surfaced first.

Core Features & Use Cases

  • Priority-driven diagnostics: deterministically checks for compile/build errors, runtime crashes, API failures, and rendering issues in order of severity.
  • Cross-component coverage: detects problems across Standalone viewer, IDE DevTools, and embedded environments to provide a holistic triage.
  • Actionable remediation: offers concrete fix recommendations and an activation flow for rapid resolution.

Quick Start

在 Claude Code 中调用 /botoolagent-ide-debug 即可开始诊断 IDE 问题。

Frequently Asked Questions about botoolagent-ide-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug IDE compile errors and runtime crashes in a web application?▼

Debugging IDE health issues starts with prioritizing fatal errors, using a stepwise triage process from P0 to P4 to deterministically check compile/build errors, runtime crashes, API failures, and rendering issues in order of severity.

What is the best way to diagnose frontend DevTools issues across multiple IDE components?▼

Diagnose frontend DevTools issues across multiple IDE components by applying cross-component coverage that detects problems across the standalone viewer, IDE DevTools, and embedded environments to deliver a holistic triage.

Does this IDE diagnostic workflow support stepwise triage from compile errors to performance issues?▼

Yes, this IDE diagnostic workflow supports stepwise triage from compile errors to performance concerns through structured diagnostic steps P0 through P4, with optional deep-mode coverage for comprehensive end-to-end environment analysis.

Can I use MCP diagnostics for an embedded IDE viewer environment?▼

Yes, you can use MCP diagnostics for embedded IDE viewer environments because the triage process applies to end-to-end IDE environments with multiple components, detecting problems across standalone viewers, IDE DevTools, and embedded setups.

How do I get actionable remediation recommendations after diagnosing IDE fatal errors?▼

To get actionable remediation recommendations after diagnosing IDE fatal errors, complete the priority-driven diagnostic steps, which offer concrete fix recommendations and an activation flow for rapid resolution of critical problems.

Related Skills

Explore More Software Engineering Skills→
TanStackTanStack
485

devtools-production

Exclude or conditionally include TanStack Devtools in production builds via Vite plugins.

Official
Intermediate
gregoryraymondgregoryraymond

solidjs-performance

Diagnose SolidJS reactivity pitfalls and apply batch, untrack, and memo patterns.

Community
Advanced
githubgithub
37.6k

chrome-devtools

Automate browser control and debugging via the Chrome DevTools MCP.

Official
Advanced
heaptracetechnologyheaptracetechnology
13

mobile-debug

Automate mobile crash triage and root-cause debugging across React Native, Flutter, and native iOS/Android.

Community
Advanced