home/categories/debugging
category focus

Debugging

Tools for finding and fixing code issues.

4271 ์Šคํ‚ฌall categories
sorting
์Šคํƒ€
current ordering strategy
query
all entries
refine the visible subset
debugging
0

lazynvim-optimization

This skill should be used when the user asks about "lazy.nvim", "plugin performance", "neovim startup time", "slow neovim", "optimize plugins", "lazy-loading", "startuptime profiling", or wants to improve Neovim performance through better plugin management.

kriscard
kriscard
tools
open
debugging
0

error-handling-auditor

Find and fix unsafe error handling in Leavn - try! force unwraps, empty catch blocks, silent try? failures

willsigmon
willsigmon
tools
open
debugging
0

code-explorer

Hybrid search strategy for finding relevant code: fast targeted search, then deep analysis if needed.

JuniYadi
JuniYadi
tools
open
debugging
0

performance-engineer

Expert in system optimization, profiling, and scalability. Specializes in eBPF, Flamegraphs, and kernel-level tuning.

404kidwiz
404kidwiz
tools
open
debugging
0

pm-08-performance

Analyse throughput, case duration, and activity sojourn times from the filtered log.

Wattysaid
Wattysaid
tools
open
debugging
0

webapp-debugger

Chrome DevTools MCPใ‚’ไฝฟ็”จใ—ใŸWebใ‚ขใƒ—ใƒชใฎใƒ‡ใƒใƒƒใ‚ฐๆ”ฏๆดใ‚นใ‚ญใƒซใ€‚ใƒ–ใƒฉใ‚ฆใ‚ถๆ“ไฝœใ€ใ‚ณใƒณใ‚ฝใƒผใƒซใƒญใ‚ฐ็›ฃ่ฆ–ใ€ใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใƒชใ‚ฏใ‚จใ‚นใƒˆๅˆ†ๆžใ€ใƒ‘ใƒ•ใ‚ฉใƒผใƒžใƒณใ‚น่จˆๆธฌใ‚’่กŒใ†ใ€‚ ไฝฟ็”จใ‚ฟใ‚คใƒŸใƒณใ‚ฐ: (1) Webใ‚ขใƒ—ใƒชใฎๅ‹•ไฝœ็ขบ่ชใƒปใƒ‡ใƒใƒƒใ‚ฐ (2) UIใฎ่‡ชๅ‹•ๆ“ไฝœใƒ†ใ‚นใƒˆ (3) ใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใ‚จใƒฉใƒผใฎ่ชฟๆŸป (4) ใ‚ณใƒณใ‚ฝใƒผใƒซใ‚จใƒฉใƒผใฎ็ขบ่ช (5) ใƒ‘ใƒ•ใ‚ฉใƒผใƒžใƒณใ‚นๅ•้กŒใฎ่จบๆ–ญ (6) ใƒ•ใ‚ฉใƒผใƒ ๅ…ฅๅŠ›ใฎ่‡ชๅ‹•ๅŒ– (7) ใ‚นใ‚ฏใƒชใƒผใƒณใ‚ทใƒงใƒƒใƒˆๅ–ๅพ—

CAPHTECH
CAPHTECH
tools
open
debugging
0

mcp-expert

Gemini Elite MCP Orchestrator. Master of Chrome DevTools, Context7 and Auto-Configuration.

YuniorGlez
YuniorGlez
tools
open
debugging
0

operability-observation

้‹็”จ่ฆณๆธฌๆ€งใฎ็ขบไฟใ€‚ใƒญใ‚ฐใ€ใƒกใƒˆใƒชใ‚ฏใ‚นใ€ใƒ˜ใƒซใ‚นใƒใ‚งใƒƒใ‚ฏใ€่จญๅฎšๆคœ่จผใงใƒใ‚ฐใ‚’ๆ‰ฑใ†่ƒฝๅŠ›ใ‚’ๆ‹…ไฟใ€‚Use when: ใƒ‡ใƒ—ใƒญใ‚คๅ‰ใƒใ‚งใƒƒใ‚ฏใ€้šœๅฎณ่ชฟๆŸปใŒๅ›ฐ้›ฃใ€ๅŽŸๅ› ไธๆ˜Žใ€ใƒญใ‚ฐ่จญ่จˆใ€ใƒกใƒˆใƒชใ‚ฏใ‚น่จญ่จˆใ€่จญๅฎš็ฎก็†ๅฎŸ่ฃ…ใ€‚

CAPHTECH
CAPHTECH
tools
open
debugging
0

exploit-development

Develop working exploits using pwntools. Includes exploit template and common patterns.

amattas
amattas
tools
open
debugging
0

cloudflare-workers

Optimize code for Cloudflare Workers free plan with 10ms CPU limit. Use when writing API routes, server code, middleware, or discussing performance optimization.

jonit-dev
jonit-dev
tools
open
debugging
0

shell-complex-test

ๆต‹่ฏ• Shell AST ๅคๆ‚ๅตŒๅฅ—็ป“ๆž„ๆฃ€ๆต‹

nonabit
nonabit
tools
open
debugging
0

javascript-pragmatic-rules

30 pragmatic rules for production JavaScript covering async operations, V8 optimization, memory management, testing, error handling, and performance. Use when writing JavaScript, optimizing performance, handling promises, or building production-grade applications. Includes promise rejection handling, V8 hidden classes, memory leak prevention, and structured testing patterns.

matthewharwood
matthewharwood
tools
open
debugging
0

diagnosing-type-errors

Analyze TypeScript errors and provide detailed diagnostics with root cause analysis and specific fix recommendations

djankies
djankies
tools
open
debugging
0

eds-performance-debugging

Guide for debugging and performance optimization of EDS blocks including error handling, FOUC prevention, Core Web Vitals optimization, and debugging workflows for Adobe Edge Delivery Services.

fastcmsdomain
fastcmsdomain
tools
open
debugging
0

obsidian-automation

This skill should be used when working on Obsidian plugins, testing plugin changes, verifying plugin UI, debugging plugin behaviour, or running automated tests against Obsidian. Also triggers on "start Obsidian", "take Obsidian screenshot", "test plugin", "run plugin command", "execute in Obsidian", or any Obsidian automation task. Use proactively during plugin development to verify changes visually.

tavva
tavva
tools
open
debugging
0

protocol-reverse-engineering

Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.

pelan05
pelan05
tools
open
debugging
0

suno-analyze

ๆ›ฒใ‚’่จญ่จˆ่ฆ–็‚นใงๅˆ†ๆžใ—ใ€analysis/{slug}.mdใซไฟๅญ˜ใ€‚ๆ›ฒใฎๆœฌ่ณชใ€ๆง‹้€ ใ€ใ‚ณใƒผใƒ‰้€ฒ่กŒใ€ใ‚ขใƒฌใƒณใ‚ธใƒกใƒณใƒˆใ‚’่จ€่ชžๅŒ–ใ™ใ‚‹ใ€‚

takish
takish
tools
open
debugging
0

analyzing-compiler-graphs

Dumps and analyzes Graal IR compiler graphs showing optimization decisions. Use BGV format with bgv2json/seafoam to inspect escape analysis, boxing removal, inlining decisions, and call node types. Reveals what compiler actually optimized vs intended. Use as last resort after basic profiling when root cause remains unclear.

antonykamp
antonykamp
tools
open
debugging
0

root-cause-tracing

Systematically trace bugs backward through call stack to find original trigger

levanminhduc
levanminhduc
tools
open
debugging
0

refacter

Refacter code using complexity analysis and hotspot detection. Use when asked to refactor code, improve code quality, reduce complexity, or identify high-risk areas that need attention.

Awannaphasch2016
Awannaphasch2016
tools
open
debugging
0

logging-guidelines

Sagebaseใฎใƒญใ‚ฎใƒณใ‚ฐ่ฆ็ด„ใจใƒ™ใ‚นใƒˆใƒ—ใƒฉใ‚ฏใƒ†ใ‚ฃใ‚นใ€‚printๆ–‡็ฆๆญขใ€loggerใฎไฝฟ็”จๅŸบๆบ–ใ€ใƒญใ‚ฐใƒฌใƒ™ใƒซใฎไฝฟใ„ๅˆ†ใ‘ใ‚’ใ‚ซใƒใƒผใ€‚ใƒญใ‚ฐๅ‡บๅŠ›ใ‚’่ฟฝๅŠ ใƒปไฟฎๆญฃใ™ใ‚‹ๆ™‚ใ€ใƒ‡ใƒใƒƒใ‚ฐใ‚ณใƒผใƒ‰ใ‚’ๆ›ธใๆ™‚ใซใ‚ขใ‚ฏใƒ†ใ‚ฃใƒ™ใƒผใƒˆใ—ใพใ™ใ€‚

sage-base
sage-base
tools
open
debugging
0

debug

Trace errors and unexpected behavior to find root causes. Use when something's broken and you don't know why.

cerico
cerico
tools
open
debugging
0

systematic-debugging

Find root cause before attempting fixes through systematic investigation phases. WHEN: MUST use when encountering bugs, test failures, errors, build failures. Invoke with "/systematic-debugging" or "debug systematically". Use ESPECIALLY after multiple failed fixes or under time pressure. WHEN NOT: Issue is already understood with clear root cause, writing new features, simple typos.

LounisBou
LounisBou
tools
open
Previous
Page 177 / 178
Next