home/categories/debugging
category focus

Debugging

Tools for finding and fixing code issues.

4271 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
2

crash-log-analyzer

Parse and analyze macOS crash logs to identify crash causes and debugging information

paleoterra
paleoterra
tools
open
debugging
2

libfuzzer

Fuzzing with libFuzzer for finding vulnerabilities in code.

plurigrid
plurigrid
tools
open
debugging
2

go-linting

Go static analysis. Routes to specific tools.

JamesPrial
JamesPrial
tools
open
debugging
2

edge-performance-optimizer

Automatically optimizes Cloudflare Workers performance during development, focusing on cold starts, bundle size, edge caching, and global latency

hirefrank
hirefrank
tools
open
debugging
2

debugging-auto

Hidden automatic debugging when something breaks - user sees simple question or "fixing..." not stack traces or technical errors

timequity
timequity
tools
open
debugging
1

security-advisor

Security Advisor for vulnerability analysis and risk assessment. Reviews code and architecture for security issues. Use this skill for security review, vulnerability assessment, or risk analysis.

Denissvgn
Denissvgn
tools
open
debugging
1

critique

Generate critical analyses of Univrs.io ecosystem releases. Use when critiquing DOL, VUDO, Spirit, ENR, CryptoSaint, learn.univrs.io, or vudo.univrs.io changes. Invoked via /critique to ask "Who benefits from this machine?"

ardeshir
ardeshir
tools
open
debugging
1

xfi-debug-analysis

Guide for debugging X-Fidelity analysis issues. Use when troubleshooting analysis failures, rule evaluation problems, VSCode extension issues, or unexpected results.

zotoio
zotoio
tools
open
debugging
1

react-performance

React performance optimization specialist. Expert in DevTools Profiler, memoization, Core Web Vitals, bundle optimization, and virtualization. Use this skill for performance bottlenecks, slow renders, large bundles, or memory issues in React applications.

ANHDOO
ANHDOO
tools
open
debugging
1

atomic-design-gluestack

Enforces atomic design methodology (atoms, molecules, organisms, templates, pages) for React Native/Expo projects using Gluestack UI. This skill should be used when creating new components, validating existing component organization, reviewing component placement decisions, or planning component architecture. Use this skill to ensure components are properly categorized, placed in correct directories, and follow composition patterns appropriate to their atomic level.

CodySwannGT
CodySwannGT
tools
open
debugging
1

performance-review

This skill should be used when the user asks to "check performance", "review for performance issues", "find slow code", "optimize", "check for memory leaks", "find N+1 queries", "check complexity", "profile code", "latency issues", or mentions improving code performance.

JesseNaranjo
JesseNaranjo
tools
open
debugging
1

code-standards

This skill should be used when the user asks about "code quality", "file size limits", "function length", "KISS", "DRY", "YAGNI", "SRP", "best practices", "clean code", "cyclomatic complexity", "code review checklist", "refactoring rules", or mentions specific thresholds for lines of code, function sizes, or code complexity metrics.

hculap
hculap
tools
open
debugging
1

performance-review

Provides performance optimization guidelines for profiling, caching, memory management, and concurrency. Use when optimizing slow code, fixing memory leaks, improving throughput, or conducting performance reviews.

kcenon
kcenon
tools
open
debugging
1

accessibility-audit

Perform WCAG accessibility audits on React components using automated tools and manual checks. Use when auditing accessibility, fixing a11y issues, or ensuring WCAG compliance.

JanSzewczyk
JanSzewczyk
tools
open
debugging
1

performance-review

Provides performance optimization guidelines for profiling, caching, memory management, and concurrency. Use when optimizing slow code, fixing memory leaks, improving throughput, or conducting performance reviews.

kcenon
kcenon
tools
open
debugging
1

picoruby-development-constraints

Documents memory limits and stdlib constraints for PicoRuby on ESP32. Use this when writing code that will run on ESP32 hardware or designing features for PicoRuby applications.

bash0C7
bash0C7
tools
open
debugging
1

native-app-performance

Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.

chrisrodz
chrisrodz
tools
open
debugging
1

performance-budget-enforcer

Monitors Lighthouse scores and JavaScript bundle sizes across deployments with automated alerts when performance thresholds are exceeded. This skill should be used when setting up performance monitoring, enforcing bundle size limits, tracking Lighthouse metrics, or adding performance regression detection. Use for performance budgets, bundle size, Lighthouse CI, performance monitoring, regression detection, or web vitals tracking.

hopeoverture
hopeoverture
tools
open
debugging
1

testing-skills-with-subagents

Use before skill deployment to verify pressure resistance via TDD RED-GREEN-REFACTOR cycle with Serena metrics tracking - measures compliance score (0.00-1.00) across pressure scenarios

krzemienski
krzemienski
tools
open
debugging
1

git-history-analyzer

Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\nuser: "I've just refactored the authentication module. Can you analyze the historical context?"\nassistant: "I'll use the git-history-analyzer agent to examine the evolution of the authentication module files."\n<commentary>Since the user wants historical context about code changes, use the git-history-analyzer agent to trace file evolution, identify contributors, and extract patterns from the git history.</commentary></example> <example>Context: The user needs to understand why certain code patterns exist.\nuser: "Why does this payment processing co

i3ringit
i3ringit
tools
open
debugging
1

repository-analysis

Deep repository analysis methodology for understanding codebase structure, dependencies, patterns, and change impact. Use when analyzing repositories for customization planning, refactoring, or understanding project architecture.

klintravis
klintravis
tools
open
debugging
1

frontend-architect

Build production-grade UI/UX with React (Next.js, Docusaurus), CSS architecture (Tailwind, Modules, Global), animations, theming, performance optimization, state management, and testing. Use when creating React components, building layouts, refactoring CSS, implementing animations, auditing accessibility, optimizing performance, setting up state management, or writing component tests.

uneezaismail
uneezaismail
tools
open
debugging
1

code-research

Conducts in-depth code research using a tiered tool strategy. Use when investigating codebases, researching libraries/APIs, debugging errors, or understanding unfamiliar code patterns.

cercova-studios
cercova-studios
tools
open
debugging
1

code-reviewer

Perform comprehensive code reviews analyzing security, performance, maintainability, and best practices. Use when reviewing code changes, pull requests, or providing code quality feedback.

elbow86
elbow86
tools
open
Previous
Page 112 / 178
Next