home/categories/debugging
category focus

Debugging

Tools for finding and fixing code issues.

4271টি স্কিলall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
178

gsd-debugger

Systematic debugging with persistent state and fresh context advantages

toonight
toonight
tools
open
debugging
169

implicit-decision-capture

Automatically capture implicit technical decisions and uncertainties encountered by AI agents during coding work. This skill logs decision points where the agent chose an approach without explicit user guidance, enabling later review and context enrichment. Use this proactively during any coding task to track "what choices I made and why."

PackmindHub
PackmindHub
tools
open
debugging
169

pattern-discovery-capture

Automatically capture recurring patterns discovered in the codebase during exploration. This skill logs implicit conventions, architectural patterns, and coding practices that are followed consistently but not formally documented. Use this proactively when you observe patterns that could become explicit standards.

PackmindHub
PackmindHub
tools
open
debugging
167

debug-prod-issues

Debug production issues on Vercel using logs, database inspection, and proper deployment waiting

different-ai
different-ai
tools
open
debugging
166

playwright-local

Build browser automation and web scraping with Playwright on your local machine. Includes stealth mode for anti-bot bypass, authenticated sessions, infinite scroll handling, screenshot/PDF generation, and residential IP advantages. Use when: automating browsers, scraping protected sites, testing with real IPs, bypassing bot detection, generating screenshots/PDFs, or troubleshooting "target closed", "element not found", or "navigation timeout" errors.

jezweb
jezweb
tools
open
debugging
166

superpowers-debug

Systematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests. Use when troubleshooting errors, failing tests, or unexpected behavior.

anthonylee991
anthonylee991
tools
open
debugging
160

performance-analysis

Measurement approaches, profiling tools, optimization patterns, and capacity planning. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizing.

rsmdt
rsmdt
tools
open
debugging
160

bug-diagnosis

Apply scientific debugging methodology through conversational investigation. Use when investigating bugs, forming hypotheses, tracing error causes, performing root cause analysis, or systematically diagnosing issues. Includes progressive disclosure patterns, observable actions principle, and user-controlled dialogue flow.

rsmdt
rsmdt
tools
open
debugging
155

idalib-analysis

Analyze binaries using IDA Pro's Python API (idalib) in headless mode. Use when examining program structure, functions, disassembly, cross-references, or strings without the GUI.

williballenthin
williballenthin
tools
open
debugging
147

testing-implementation

Comprehensive testing strategies, test automation, quality assurance with JUnit, MockK, Jest. Use for testing, test, qa, quality, coverage tags. Provides test patterns, validation commands, coverage targets.

jpicklyk
jpicklyk
tools
open
debugging
144

capemon-developer

Expert capability for navigating, modifying, and extending the capemon malware monitoring codebase. Includes deep knowledge of Windows API hooking, PE structures, and the CAPEv2 sandbox architecture.

kevoreilly
kevoreilly
tools
open
debugging
138

web-perf

Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (FCP, LCP, TBT, CLS, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.

elithrar
elithrar
tools
open
debugging
135

react-best-practices

React and Next.js performance optimization guidelines tuned by gracefullight, forked from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

first-fluke
first-fluke
tools
open
debugging
134

monitor

Track production app health and catch issues before users complain. Use after deploying, to check app status, or when investigating user reports. Covers error tracking, uptime monitoring, and metrics for non-technical founders.

whawkinsiv
whawkinsiv
tools
open
debugging
131

browsing

Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool

obra
obra
tools
open
debugging
131

browser

Minimal Chrome DevTools Protocol tools for browser automation and scraping. Use when you need to start Chrome, navigate pages, execute JavaScript, take screenshots, or interactively pick DOM elements.

julianromli
julianromli
tools
open
debugging
130

java-python-code-reviewer

Comprehensive code reviewer for Java and Python implementations focusing on correctness, efficiency, code quality, and algorithmic optimization. Reviews LeetCode solutions, data structures, and algorithm implementations. Use when reviewing code, checking solutions, or providing feedback on implementations.

yennanliu
yennanliu
tools
open
debugging
124

performance-testing

Test application performance, scalability, and resilience. Use when planning load testing, stress testing, or optimizing system performance.

proffesor-for-testing
proffesor-for-testing
tools
open
debugging
124

visual-testing-advanced

Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.

proffesor-for-testing
proffesor-for-testing
tools
open
debugging
124

mutation-testing

Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate. Use when evaluating test quality, identifying weak tests, or proving tests actually catch bugs.

proffesor-for-testing
proffesor-for-testing
tools
open
debugging
124

brutal-honesty-review

Unvarnished technical criticism combining Linus Torvalds' precision, Gordon Ramsay's standards, and James Bach's BS-detection. Use when code/tests need harsh reality checks, certification schemes smell fishy, or technical decisions lack rigor. No sugar-coating, just surgical truth about what's broken and why.

proffesor-for-testing
proffesor-for-testing
tools
open
debugging
124

sherlock-review

Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic observation.

proffesor-for-testing
proffesor-for-testing
tools
open
debugging
124

risk-based-testing

Focus testing effort on highest-risk areas using risk assessment and prioritization. Use when planning test strategy, allocating testing resources, or making coverage decisions.

proffesor-for-testing
proffesor-for-testing
tools
open
debugging
123

testing-coverage

Guide for writing tests and achieving high code coverage for CosmWasm contracts. Use when creating unit tests, integration tests, or analyzing coverage reports.

axone-protocol
axone-protocol
tools
open
Previous
Page 63 / 178
Next