debugging
3
analyzing-root-causes
Root cause analysis with 5 Whys methodology. Triggers: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
thkt
tools
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
3
memory-hierarchy
Complete reference for Claude Code's memory management system including all file types, locations, import syntax, and best practices. Use when planning or managing CLAUDE.md and related memory files.
yebot
tools
debugging
3
analyze-video-performance-skill
Analyze your uploaded YouTube videos' performance against competitor benchmarks using Playwright MCP. Use when asked to review video analytics, compare performance, check how a video is doing, or reflect on a video's success.
SGobet
tools
debugging
3
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Implements scientific method for debugging with root cause analysis.
Bbeierle12
tools
debugging
3
performance-profiling
Profile CPU, memory, and I/O usage to identify bottlenecks, analyze execution traces, and diagnose performance issues
dasien
tools
debugging
3
automating-browser
Browser automation using agent-browser CLI. Best for E2E testing, demos, screenshots. Triggers: browser automation, E2E test, ブラウザ操作, スクリーンショット, demo, manual testing.
thkt
tools
debugging
3
agentuity-cli-profile-current
Show the name of the currently active profile
agentuity
tools
debugging
3
performing-penetration-testing
Perform security penetration testing to identify vulnerabilities. Use when conducting security assessments. Trigger with 'run pentest', 'security testing', or 'find vulnerabilities'.
BbgnsurfTech
tools
debugging
3
codebase-analyzer
Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use this when you need to understand HOW code works in the existing codebase.
d-o-hub
tools
debugging
3
reviewing-type-safety
TypeScript type safety patterns and best practices for maximum type coverage. Use when reviewing TypeScript code for type issues, eliminating `any` types, or when user mentions type safety, 型安全, 型カバレッジ, strict mode.
thkt
tools
debugging
3
advisor-triggers
Detects when user requests warrant critical analysis via /advise command
akaszubski
tools
debugging
3
pattern-detector
Universal pattern detector - learns from ANY codebase through sample analysis
jhlee0409
tools
debugging
3
security-review
Review Dart FFI code for security issues in cryptographic contexts. Use when reviewing code changes, checking for memory leaks, verifying secure memory handling, or auditing cryptographic code.
djx-y-z
tools
debugging
3
memory-management-optimization
Debug memory leaks, profile memory usage, optimize allocations. Use when heap grows unexpectedly, OOM errors occur, or profiling shows memory bottleneck. Covers C++ (Valgrind, ASAN, RAII), Python (tracemalloc, objgraph), and general patterns.
HTRamsey
tools
debugging
3
five-whys
Root cause analysis for software bugs using the 5 Whys technique. Use when the user wants to find the underlying cause of a bug, error, or technical issue. Triggers include phrases like "why is this happening", "root cause", "debug this", or when investigating software problems.
iamhenry
tools
debugging
3
static-vulnerability-analysis
Methodical approach to finding security vulnerabilities through source code review and static analysis
macaugh
tools
debugging
3
chrome-devtools-optimizer
Reduce token consumption by 70-80% when using Chrome DevTools MCP through smart snapshot strategies and optional Gemini Flash vision processing. Includes decision trees, pattern guides, and automated optimization workflows.
diegocconsolini
tools
debugging
3
mcp-chrome-devtools
Automate Chrome browser via DevTools Protocol. Navigate pages, interact with elements, inspect network/console, analyze performance, and capture screenshots for web testing and automation tasks.
ulasbilgen
tools
debugging
3
cluso-inspector
Visual element selector for extracting HTML, screenshots, and context from web pages. Use when you need to see what the user is referring to, when clarification is needed about UI elements, or when the user offers to show you something visually.
jasonkneen
tools