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
0

performance-hunter

Find and fix performance bottlenecks in ANY language or framework. Use when applications are slow, memory usage is high, or you need to optimize critical paths.

j0KZ
j0KZ
tools
open
debugging
0

project-analysis

Analyzes any project to understand its structure, tech stack, patterns, and conventions. Use when starting work on a new codebase, onboarding, or when asked "how does this project work?" or "what's the architecture?"

meeezus
meeezus
tools
open
debugging
0

screen-report

Screen Loggerのログ分析と日報生成。専用スクリプトを使用して分析を実行。

hirose30
hirose30
tools
open
debugging
0

spec-performance

This skill should be used when the user asks about "slow specs", "test performance", "parallel tests", "spec profiling", "let vs let!", "build vs create", "test optimization", or needs guidance on making RSpec tests faster.

bastos
bastos
tools
open
debugging
0

prometheus-ui

Prometheus UI Development Skill for PCGS 2.0. Use for ANY UI work in Prometheus: (1) Positioning/layout changes using coordinate system, (2) Component creation within Content Zone, (3) Style modifications within doctrine, (4) Viewport configuration, (5) Frame element awareness. Enforces UI_DOCTRINE.md immutable elements. Triggers: position, layout, align, move, resize, coordinate, grid unit, vw, vh, UI component, Content Zone, frame, PKE interface.

PrometheusDevCreator
PrometheusDevCreator
tools
open
debugging
0

debug

Systematically analyze and fix bugs, errors, and unexpected behavior. Use when the user reports bugs, error messages, crashes, test failures, unexpected behavior, or performance issues.

ririnto
ririnto
tools
open
debugging
0

bug-analysis

Analyzes software bugs including root cause identification, severity assessment, impact analysis, reproduction steps validation, and fix recommendations. Performs bug triage, categorization, duplicate detection, and regression analysis. Use when investigating bugs, analyzing crash reports, triaging issues, debugging problems, reviewing error logs, or when users mention "analyze bug", "investigate issue", "debug problem", "bug report", "crash analysis", "root cause analysis", or "fix recommendation".

DauQuangThanh
DauQuangThanh
tools
open
debugging
0

forensic-coder

Comprehensive forensic analysis skill for enterprise codebases across Azure, Dynamics 365, C#, SAP, Mulesoft, Power Platform, and more. Covers security, performance, architecture, and compliance in multi-language, multi-system environments. Use this for deep-dive audits and refactoring insights.

acornsoft
acornsoft
tools
open
debugging
0

react-discovery

Research and understand React projects and features. Use when asked to explore a React codebase, check if a feature exists, understand component relationships, or map project structure. Specialized for React/Vite/Next.js projects.

tienchinh21
tienchinh21
tools
open
debugging
0

log-debug-issue

Log problems, bugs, and debugging processes with solutions. Use when encountering issues during development, debugging problems, or documenting solutions for future reference. Maintains DEBUG_LOG.md with structured problem-solution entries.

dudusoar
dudusoar
tools
open
debugging
0

project-analyzer

Systematically analyze a codebase to understand its structure, purpose, technologies, and architecture. Use this skill when users ask to "analyze this project", "explain this codebase", "what does this project do", or need a comprehensive overview of repository contents.

alexss200010
alexss200010
tools
open
debugging
0

issue-fixer

This skill provides a systematic approach for investigating and fixing bugs and issues in the codebase. Use this skill when users report bugs, unexpected behavior, test failures, or request fixes for specific issues. The skill guides through issue registration, root cause analysis, impact assessment, minimal code changes, quality validation, and E2E testing.

cyberelf
cyberelf
tools
open
debugging
0

timeline-forensics

Create comprehensive forensic timelines from multiple data sources. Use when reconstructing event sequences, correlating activities across sources, or visualizing incident progression. Supports super timeline creation and analysis.

SherifEldeeb
SherifEldeeb
tools
open
debugging
0

systematic-debugging

This skill should be used when the user reports a "bug", "not working", "fix this", "debug", "test failing", or when investigating unexpected behavior. Four-phase framework ensuring root cause understanding before attempting solutions.

pproenca
pproenca
tools
open
debugging
0

review-project

Analyze project health including structural issues, security vulnerabilities, performance concerns, and code stability metrics. Use when auditing codebases, reviewing project quality, checking for security issues, identifying architectural problems, measuring code health, or generating quality reports.

runxgalee
runxgalee
tools
open
debugging
0

react-best-practices

Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering. Use when optimizing React apps, reviewing performance, or refactoring components.

gotekna
gotekna
tools
open
debugging
0

debug-phase

Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)

Sjdjdiejdrirhdkjej
Sjdjdiejdrirhdkjej
tools
open
debugging
0

architecture-guardian

Review architecture decisions and code changes against documented architecture principles. Use this skill before implementing new features or refactoring existing code to ensure compliance with layer boundaries, separation of concerns, and design patterns. Should be invoked when user requests "architecture review" or before making significant changes.

JoeCotellese
JoeCotellese
tools
open
debugging
0

architecture-health

Diagnoses project health, architecture risks, and technical debt. Use when starting a new session or analyzing the codebase structure.

DeruL0
DeruL0
tools
open
debugging
0

debugging-wizard

Systematic debugging expert for all languages and frameworks. Invoke for error investigation, troubleshooting, log analysis, root cause analysis. Keywords: debug, error, bug, traceback, exception, breakpoint.

franroa
franroa
tools
open
debugging
0

debugger

Diagnose and fix runtime issues, errors, and bugs through systematic reproduction, root cause analysis, and targeted fixes. Use for debugging production issues, test failures, performance problems, and any type of software defect.

d-oit
d-oit
tools
open
debugging
0

claude-code-analyzer

Analyze Claude Code usage patterns, project structure, and discover community resources for workflow optimization

kriscard
kriscard
tools
open
debugging
0

performance-analyzer

Analyzes code for performance issues including inefficient algorithms, unnecessary computations, memory leaks, large file sizes, slow queries, and missing caching. Returns structured performance issue reports with optimization suggestions.

lexicalninja
lexicalninja
tools
open
debugging
0

ci-triage

Quick CI/CD failure diagnosis. Use when builds fail.

ethosengine
ethosengine
tools
open
Previous
Page 135 / 178
Next