skills.homes logoskills.homescapability registry
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
121

lightweight-implementation-analysis-protocol

This skill should be used when fixing bugs, implementing features, debugging issues, or making code changes. Ensures understanding of code flow before implementation by: (1) Tracing execution path with specific file:line references, (2) Creating lightweight text diagrams showing class.method() flows, (3) Verifying understanding with user. Prevents wasted effort from assumptions or guessing. Triggers when users request: bug fixes, feature implementations, refactoring, TDD cycles, debugging, code analysis.

NTCoding
NTCoding
tools
open
debugging
121

observability-first-debugging

Systematic debugging methodology that eliminates guessing and speculation. Add instrumentation to gather specific data that fully explains the problem. Evidence before hypothesis. Observation before solution.

NTCoding
NTCoding
tools
open
debugging
121

tabz-development

Patterns for building and debugging TabzChrome itself. Use when working on Terminal.tsx, xterm.js integration, WebSocket I/O, resize handling, or any TabzChrome extension/backend code.

GGPrompts
GGPrompts
tools
open
debugging
115

performance-optimizer

Performance analysis, profiling techniques, bottleneck identification, and optimization strategies for code and systems. Use when the user needs to improve performance, reduce resource usage, or identify and fix performance bottlenecks.

einverne
einverne
tools
open
debugging
115

debug-helper

Systematic debugging strategies, troubleshooting methodologies, and problem-solving techniques for code and system issues. Use when the user encounters bugs, errors, or unexpected behavior and needs help diagnosing and resolving problems.

einverne
einverne
tools
open
debugging
114

uloop-get-logs

Check Unity Console logs. Use when user says: 'check the logs', 'what's in the console', 'show me the errors', 'why did it fail', 'what happened', 'see what printed'. Retrieves errors, warnings, and Debug.Log messages.

hatayama
hatayama
tools
open
debugging
114

uloop-get-logs

Get Unity Console output including errors, warnings, and Debug.Log messages. Use when you need to: (1) Check for compile errors or runtime exceptions after code changes, (2) See what Debug.Log printed during execution, (3) Find NullReferenceException, MissingComponentException, or other error messages, (4) Investigate why something failed in Unity Editor.

hatayama
hatayama
tools
open
debugging
110

netbox-mcp-testing

This skill should be used when systematically testing the NetBox MCP server after code changes or to validate tool functionality. Provides structured protocol for discovering and testing MCP tools with a live NetBox instance, with emphasis on performance monitoring and comprehensive reporting.

netboxlabs
netboxlabs
tools
open
debugging
109

nextjs-devtools

Next.js development tooling via MCP. Inspect routes, components, build info, and debug Next.js apps. Use when working on Next.js applications, debugging routing, or inspecting app structure. NOT for general React or non-Next.js projects.

panaversity
panaversity
tools
open
debugging
109

building-with-observability

Build Kubernetes observability stacks with Prometheus, Grafana, OpenTelemetry, Jaeger, and Loki. Use when implementing metrics, tracing, logging, SRE practices, or cost engineering for cloud-native applications.

panaversity
panaversity
tools
open
debugging
109

systematic-debugging

Systematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical issue before proposing fixes. Covers root cause investigation, pattern analysis, hypothesis testing, and fix implementation. Use ESPECIALLY when under time pressure, just one quick fix seems obvious, or you've already tried multiple fixes. NOT for exploratory code reading.

panaversity
panaversity
tools
open
debugging
107

debugging-strategies

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

Microck
Microck
tools
open
debugging
107

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Microck
Microck
tools
open
debugging
107

ffuf-web-fuzzing

Expert guidance for ffuf web fuzzing during penetration testing, including authenticated fuzzing with raw requests, auto-calibration, and result analysis

Microck
Microck
tools
open
debugging
107

modern-javascript-patterns

Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.

Microck
Microck
tools
open
debugging
106

code-review-assistant

Perform structured, actionable code reviews for Python code with clear findings and suggestions.

dmitriiweb
dmitriiweb
tools
open
debugging
106

perf-prof

使用perf-prof进行Linux系统问题分析。perf-prof是基于perf_event的系统级分析工具，事件在内存中实时处理，可长期运行。触发场景：(1) CPU使用率高、热点分析 (2) 进程状态异常(D/S状态多) (3) 延迟抖动、响应慢 (4) 内存泄露或增长异常 (5) 块设备IO慢 (6) 虚拟机性能问题 (7) 事件聚合统计。核心分析器：profile(CPU采样)、task-state(进程状态)、multi-trace(延迟分析)、kmemleak(内存泄露)、blktrace(IO延迟)、top/sql(聚合统计)、kvm-exit(虚拟化退出)、rundelay(调度延迟)、syscalls(系统调用耗时)。适用于：性能问题定位、内核/应用开发调试、学习理解Linux内核机制（调度、内存、IO、中断等）。

OpenCloudOS
OpenCloudOS
tools
open
debugging
103

code-review

Performs thorough code reviews with focus on best practices, security, performance, and maintainability. Use this skill when reviewing pull requests, auditing code quality, or getting feedback on implementations.

femto
femto
tools
open
debugging
101

react-performance

Optimization strategies for React applications (Client & Server).

HoangNguyen0403
HoangNguyen0403
tools
open
debugging
101

react-hooks

Best practices for React Hooks usage and custom hook creation.

HoangNguyen0403
HoangNguyen0403
tools
open
debugging
98

codebase-explorer

Explore SaneBar codebase efficiently using Explore subagent. Use when searching for code, understanding architecture, finding patterns, or locating implementations. Keywords: find, search, where is, how does, explore, understand, architecture, codebase

sane-apps
sane-apps
tools
open
Previous
Page 64 / 178
Next