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
1K

testing-visual-regression

Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

performing-visual-regression-testing

This skill enables Claude to execute visual regression tests using tools like Percy, Chromatic, and BackstopJS. It captures screenshots, compares them against baselines, and analyzes visual differences to identify unintended UI changes. Use this skill when the user requests visual testing, UI change verification, or regression testing for a web application or component. Trigger phrases include "visual test," "UI regression," "check visual changes," or "/visual-test".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

analyzing-test-coverage

Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

performing-visual-regression-testing

This skill enables Claude to execute visual regression tests using tools like Percy, Chromatic, and BackstopJS. It captures screenshots, compares them against baselines, and analyzes visual differences to identify unintended UI changes. Use this skill when the user requests visual testing, UI change verification, or regression testing for a web application or component. Trigger phrases include "visual test," "UI regression," "check visual changes," or "/visual-test".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

clay-debug-bundle

Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

firecrawl-advanced-troubleshooting

Apply FireCrawl advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for FireCrawl support escalation. Trigger with phrases like "firecrawl hard bug", "firecrawl mystery error", "firecrawl impossible to debug", "difficult firecrawl issue", "firecrawl deep debug".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

clerk-debug-bundle

Collect comprehensive debug information for Clerk issues. Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues. Trigger with phrases like "clerk debug", "clerk diagnostics", "clerk support ticket", "clerk troubleshooting".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

clay-performance-tuning

Optimize Clay API performance with caching, batching, and connection pooling. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Clay integrations. Trigger with phrases like "clay performance", "optimize clay", "clay latency", "clay caching", "clay slow", "clay batch".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

juicebox-debug-bundle

Collect Juicebox debug evidence for support. Use when creating support tickets, gathering diagnostic info, or preparing error reports for Juicebox support team. Trigger with phrases like "juicebox debug info", "juicebox support bundle", "collect juicebox diagnostics", "juicebox troubleshooting".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

detecting-sql-injection-vulnerabilities

This skill enables Claude to detect SQL injection vulnerabilities in code. It uses the sql-injection-detector plugin to analyze codebases, identify potential SQL injection flaws, and provide remediation guidance. Use this skill when the user asks to find SQL injection vulnerabilities, scan for SQL injection, or check code for SQL injection risks. The skill is triggered by phrases like "detect SQL injection", "scan for SQLi", or "check for SQL injection vulnerabilities".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

firecrawl-common-errors

Diagnose and fix FireCrawl common errors and exceptions. Use when encountering FireCrawl errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "firecrawl error", "fix firecrawl", "firecrawl not working", "debug firecrawl".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

sql-injection-detector

Sql Injection Detector - Auto-activating skill for Security Fundamentals. Triggers on: sql injection detector, sql injection detector Part of the Security Fundamentals skill category.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

detecting-memory-leaks

This skill enables Claude to detect potential memory leaks and analyze memory usage patterns in code. It is triggered when the user requests "detect memory leaks", "analyze memory usage", or similar phrases related to memory leak detection and performance analysis. The skill identifies potential issues such as unremoved event listeners, closures preventing garbage collection, uncancelled timers, unbounded cache growth, circular references, detached DOM nodes, and unnecessary global state accumulation. It then provides detailed fix recommendations. Use this skill to proactively identify and resolve memory leaks, improving application performance and stability.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

detecting-memory-leaks

This skill enables Claude to detect potential memory leaks and analyze memory usage patterns in code. It is triggered when the user requests "detect memory leaks", "analyze memory usage", or similar phrases related to memory leak detection and performance analysis. The skill identifies potential issues such as unremoved event listeners, closures preventing garbage collection, uncancelled timers, unbounded cache growth, circular references, detached DOM nodes, and unnecessary global state accumulation. It then provides detailed fix recommendations. Use this skill to proactively identify and resolve memory leaks, improving application performance and stability.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

network-latency-tester

Network Latency Tester - Auto-activating skill for Performance Testing. Triggers on: network latency tester, network latency tester Part of the Performance Testing skill category.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

firecrawl-hello-world

Create a minimal working FireCrawl example. Use when starting a new FireCrawl integration, testing your setup, or learning basic FireCrawl API patterns. Trigger with phrases like "firecrawl hello world", "firecrawl example", "firecrawl quick start", "simple firecrawl code".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

linear-incident-runbook

Production incident response procedures for Linear integrations. Use when handling production issues, diagnosing outages, or responding to Linear-related incidents. Trigger with phrases like "linear incident", "linear outage", "linear production issue", "debug linear production", "linear down".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

scanning-for-accessibility-issues

This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

clay-common-errors

Diagnose and fix Clay common errors and exceptions. Use when encountering Clay errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "clay error", "fix clay", "clay not working", "debug clay".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

scanning-for-data-privacy-issues

This skill enables Claude to automatically scan code and configuration files for potential data privacy vulnerabilities using the data-privacy-scanner plugin. It identifies sensitive data exposure, compliance violations, and other privacy-related risks. Use this skill when the user requests to "scan for data privacy issues", "check privacy compliance", "find PII leaks", "identify GDPR violations", or needs a "privacy audit" of their codebase. The skill is most effective when used on projects involving personal data, financial information, or health records.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

openrouter-usage-analytics

Track and analyze OpenRouter usage patterns. Use when optimizing costs or understanding usage. Trigger with phrases like 'openrouter analytics', 'openrouter usage', 'openrouter metrics', 'track openrouter'.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

detecting-sql-injection-vulnerabilities

This skill enables Claude to detect SQL injection vulnerabilities in code. It uses the sql-injection-detector plugin to analyze codebases, identify potential SQL injection flaws, and provide remediation guidance. Use this skill when the user asks to find SQL injection vulnerabilities, scan for SQL injection, or check code for SQL injection risks. The skill is triggered by phrases like "detect SQL injection", "scan for SQLi", or "check for SQL injection vulnerabilities".

jeremylongshore
jeremylongshore
tools
open
debugging
1K

scanning-for-xss-vulnerabilities

This skill enables Claude to automatically scan for XSS (Cross-Site Scripting) vulnerabilities in code. It is triggered when the user requests to "scan for XSS vulnerabilities", "check for XSS", or uses the command "/xss". The skill identifies reflected, stored, and DOM-based XSS vulnerabilities. It analyzes HTML, JavaScript, CSS, and URL contexts to detect potential exploits and suggests safe proof-of-concept payloads. This skill is best used during code review, security audits, and before deploying web applications to production.

jeremylongshore
jeremylongshore
tools
open
debugging
1K

linear-debug-bundle

Comprehensive debugging toolkit for Linear integrations. Use when setting up logging, tracing API calls, or building debug utilities for Linear. Trigger with phrases like "debug linear integration", "linear logging", "trace linear API", "linear debugging tools", "linear troubleshooting".

jeremylongshore
jeremylongshore
tools
open
Previous
Page 56 / 178
Next