debugging
38
technical-debt-assessment
Assess, quantify, and prioritize technical debt using code analysis, metrics, and impact analysis. Use when planning refactoring, evaluating codebases, or making architectural decisions.
aj-geddes
tools
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
38
network-debugging
Debug network issues using browser tools and network analysis. Diagnose connection problems, latency, and data transmission issues.
aj-geddes
tools
debugging
38
browser-debugging
Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.
aj-geddes
tools
debugging
38
accessibility-testing
Test web applications for WCAG compliance and ensure usability for users with disabilities. Use for accessibility test, a11y, axe, ARIA, keyboard navigation, screen reader compatibility, and WCAG validation.
aj-geddes
tools
debugging
38
visual-regression-testing
Detect unintended visual changes in UI by comparing screenshots across versions. Use for visual regression, screenshot diff, Percy, Chromatic, UI testing, and visual validation.
aj-geddes
tools
debugging
38
performance-testing
Design and execute performance tests to measure response times, throughput, and resource utilization. Use for performance test, load test, JMeter, k6, benchmark, latency testing, and scalability analysis.
aj-geddes
tools
debugging
38
profiling-optimization
Profile application performance, identify bottlenecks, and optimize hot paths using CPU profiling, flame graphs, and benchmarking. Use when investigating performance issues or optimizing critical code paths.
aj-geddes
tools
debugging
38
code-metrics-analysis
Analyze code complexity, cyclomatic complexity, maintainability index, and code churn using metrics tools. Use when assessing code quality, identifying refactoring candidates, or monitoring technical debt.
aj-geddes
tools
debugging
38
intermittent-issue-debugging
Debug issues that occur sporadically and are hard to reproduce. Use monitoring and systematic investigation to identify root causes of flaky behavior.
aj-geddes
tools
debugging
38
memory-optimization
Profile and optimize application memory usage. Identify memory leaks, reduce memory footprint, and improve efficiency for better performance and reliability.
aj-geddes
tools
debugging
38
web-performance-optimization
Optimize web application performance using code splitting, lazy loading, caching, compression, and monitoring. Use when improving Core Web Vitals and user experience.
aj-geddes
tools
debugging
38
performance-regression-debugging
Identify and debug performance regressions from code changes. Use comparison and profiling to locate what degraded performance and restore baseline metrics.
aj-geddes
tools
debugging
38
web-performance-audit
Conduct comprehensive web performance audits. Measure page speed, identify bottlenecks, and recommend optimizations to improve user experience and SEO.
aj-geddes
tools
debugging
38
memory-leak-detection
Detect and fix memory leaks using heap snapshots, memory profiling, and leak detection tools. Use when investigating memory growth, OOM errors, or optimizing memory usage.
aj-geddes
tools
debugging
38
log-analysis
Analyze application and system logs to identify errors, patterns, and root causes. Use log aggregation tools and structured logging for effective debugging.
aj-geddes
tools
debugging
37
nextjs-security-scan
Comprehensive security vulnerability scanner for Next.js and TypeScript/JavaScript projects. Detects OWASP Top 10 vulnerabilities, XSS, injection flaws, authentication issues, hardcoded secrets, and Next.js-specific security problems. Audits dependencies for known CVEs and generates actionable security reports.
sugarforever
tools
debugging
37
debug-helper
Systematic debugging approach for identifying and fixing issues
athola
tools
debugging
37
dojo-debug
Use when debugging and troubleshooting dojo.js applications. Triggers: dojo error, torii connection, entity not found, type mismatch, debug dojo, troubleshoot, subscription error, sync issues
dojoengine
tools
debugging
36
mcp-inspector
Test Model Context Protocol (MCP) servers using the MCP Inspector CLI with correct syntax
JuliaSMLM
tools
debugging
34
mutation-testing
Use PIT (Pitest) mutation testing to identify weak tests and improve test quality in Java projects. Finds tests that pass but don't actually verify behavior correctly. Use when improving test suite quality beyond line coverage metrics.
bitsoex
tools
debugging
34
test-augmentation
Validates and improves test coverage for code changes. Checks coverage thresholds, identifies untested code paths, and provides guidance on writing effective tests. Use after making code changes or when improving test quality.
bitsoex
tools
debugging
34
resource-analysis
Analyze system resource usage data from sosreport archives, extracting memory statistics, CPU load averages, disk space utilization, and process information from the sosreport directory structure to diagnose resource exhaustion, performance bottlenecks, and capacity issues
openshift-eng
tools