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

wtf

Guide for diagnosing lsp errors. This skill should be used when users wants to debug a lsp/diagnostic errors, warnings, or exceptions and get clear explanations and potential solutions. <prompt-triggers> <trigger>"Why am i getting this [diagnostic error]?"</trigger> <trigger>"how do i fix this [lsp error]"</trigger> </prompt-triggers>

0xKahi
0xKahi
tools
open
debugging
0

oe-trace-and-fallback-triage

Debug and eliminate fallback/generic-stub replies quickly. Use when you see empty assistant replies, โ€œThanks for your messageโ€ฆโ€ stubs, or โ€œno specific information availableโ€ messages. Produces a minimal reproduction (test or deterministic trace) and pinpoints the fallback source + trigger.

shami-ah
shami-ah
tools
open
debugging
0

n-plus-one-detection

Detects N+1 query problems in GraphQL resolvers and TypeScript code. Checks for missing DataLoader usage, sequential database queries in loops, and resolver batching opportunities. Use before committing GraphQL resolvers or during performance reviews.

meriley
meriley
tools
open
debugging
0

coihuin-compress

Context compression for long coding sessions. Creates checkpoints (state snapshots) and maintains them as you work.

mabrax
mabrax
tools
open
debugging
0

root-cause-tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Ramblurr
Ramblurr
tools
open
debugging
0

troubleshooting

Debug event flows systematically from EventSource to Workflow. Use diagnostic commands and logging levels to isolate failures in production event systems.

adaptive-enforcement-lab
adaptive-enforcement-lab
tools
open
debugging
0

crawl

ๆ นๆฎ็”จๆˆท้œ€ๆฑ‚๏ผŒไฝฟ็”จๅทฒ็ป็™ปๅฝ•็š„ๆต่งˆๅ™จ๏ผŒๅŸบไบŽchrome-devtools ๅทฅๅ…ท็š„ๆ–นๅผๆฅไปŽๆต่งˆๅ™จไธญ่Žทๅ–็”จๆˆท้œ€่ฆ็š„ๅ†…ๅฎน๏ผŒๆ”ฏๆŒๆ–‡็ซ ๅ†…ๅฎนๆๅ–ๅ’Œๆ‰น้‡ๅค„็†ใ€‚ไป…็”จๆฅ่Žทๅ–้‚ฃไบ›้œ€่ฆ็™ปๅฝ•ๅŽๆ‰่ƒฝๅฎŒๆ•ด่ฎฟ้—ฎ็š„็ฝ‘็ซ™ใ€‚

flyingtimes
flyingtimes
tools
open
debugging
0

web-standards

Static HTML/CSS/ARIA analysis without requiring a browser. Use this skill when analyzing code for semantic HTML issues, ARIA validity, landmark structure, heading hierarchy, form labeling, or any accessibility problems detectable from source code. Queries aria-mcp for ARIA rules and wcag-mcp for success criteria mapping. Part of the a11y-orchestrator workflow.

joe-watkins
joe-watkins
tools
open
debugging
0

malware-forensics

Analyze malware samples for forensic investigation. Use when investigating malware infections, determining malware capabilities, extracting IOCs, or understanding attack techniques. Supports static and dynamic analysis of executables, scripts, and documents.

SherifEldeeb
SherifEldeeb
tools
open
debugging
0

error-analysis

This skill should be used when analyzing errors, stack traces, and logs to identify root causes and implement fixes.

jayteealao
jayteealao
tools
open
debugging
0

performance-profiler

Profile and optimize application performance. Use when diagnosing slow response times, detecting memory leaks, analyzing CPU hotspots, optimizing bundle size, or measuring Core Web Vitals.

j0KZ
j0KZ
tools
open
debugging
0

root-cause-tracing

Systematically trace bugs backward through call stack to find original trigger

yousufjoyian
yousufjoyian
tools
open
debugging
0

tui-debugger

Debug TUI (Text User Interface) applications through visual observation and semantic inspection. Use when: (1) debugging rendering issues in terminal UIs, (2) troubleshooting widget behavior or key bindings, (3) diagnosing data flow issues where updates aren't appearing in widgets, (4) investigating layout problems, (5) any TUI application debugging where you need to observe runtime state. Supports Textual (Python) with deep semantic inspection, and any TUI via mcp-tui-server visual observation.

get2knowio
get2knowio
tools
open
debugging
0

smart-context

**SMART CONTEXT v1.0** - '์ปจํ…์ŠคํŠธ', '๊ด€๋ จ ์ฝ”๋“œ', '์ฐธ์กฐ', 'ํ† ํฐ ์ ˆ์•ฝ', 'ํšจ์œจ์  ๋ถ„์„' ์š”์ฒญ ์‹œ ์ž๋™ ๋ฐœ๋™. codebase-graph ๊ธฐ๋ฐ˜์œผ๋กœ ํ•„์š”ํ•œ ์ปจํ…์ŠคํŠธ๋งŒ ์„ ํƒ์  ์ถ”์ถœ. ํ† ํฐ 72% ์ ˆ๊ฐ, ์ •ํ™•๋„ 92% ๋‹ฌ์„ฑ. ๋ชจ๋“  ์ฝ”๋“œ ๋ถ„์„ ์ž‘์—…์˜ ๊ธฐ๋ฐ˜ ๋ ˆ์ด์–ด.

monicajeon28
monicajeon28
tools
open
debugging
0

logrocket

Implements session replay and error tracking with LogRocket for debugging user issues. Use when adding session recording, error monitoring, and performance tracking to React applications.

mgd34msu
mgd34msu
tools
open
debugging
0

perf-analyzer

Performance analysis, bundle size tracking, and optimization suggestions

alexanderjamesmcleod
alexanderjamesmcleod
tools
open
debugging
0

observability

Telemetry, metrics, tracing, and observability for Elixir/BEAM applications

layeddie
layeddie
tools
open
debugging
0

check-links

Analyze and validate links and buttons on web pages. Use when users ask to check links, verify button hrefs, find empty links, detect javascript:void links, find broken navigation, or audit clickable elements. Detects empty href, javascript:void(0), hash-only links, missing href attributes, and non-accessible buttons.

leobrival
leobrival
tools
open
debugging
0

debugger

Use when the root cause is unclear. Trace the failure back through the call stack and isolate the first bad state.

rozwer
rozwer
tools
open
debugging
0

chrome-devtools-debugger

chrome-devtools-mcp ใ‚’ไฝฟใฃใฆWebใ‚ตใ‚คใƒˆใฎๅ•้กŒใ‚’ไฝ“็ณป็š„ใซใƒ‡ใƒใƒƒใ‚ฐใ—ใพใ™ใ€‚ใƒใƒƒใƒˆใƒฏใƒผใ‚ฏใ‚จใƒฉใƒผใ€ใ‚ณใƒณใ‚ฝใƒผใƒซใ‚จใƒฉใƒผใ€ใƒ‘ใƒ•ใ‚ฉใƒผใƒžใƒณใ‚นๅ•้กŒใ€UI/UXใฎๅ•้กŒใ‚’่ชฟๆŸปใ™ใ‚‹้š›ใซไฝฟ็”จใ—ใพใ™ใ€‚

hidari
hidari
tools
open
debugging
0

root-cause-tracing

This skill should be used when the user asks to "find the root cause", "trace the bug", "why is this happening", "where does this come from", or when errors occur deep in the call stack. Systematically traces backward to identify the source.

pproenca
pproenca
tools
open
debugging
0

reviewing-security

Automated tooling and detection patterns for JavaScript/TypeScript security vulnerabilities. Provides scan commands, vulnerability patterns, and severity mappingโ€”not output formatting or workflow.

djankies
djankies
tools
open
Previous
Page 161 / 178
Next