- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
ccxt
by 2025Emma
CCXT cryptocurrency trading library. Use for cryptocurrency exchange APIs, trading, market data, order management, and crypto trading automation across 150+ exchanges. Supports JavaScript/Python/PHP.
ai-development-guide
by shinpr
Technical decision criteria, anti-pattern detection, debugging techniques, and quality check workflow. Use when making technical decisions, detecting code smells, or performing quality assurance.
testing-principles
by shinpr
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
coding-principles
by shinpr
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
task-analyzer
by shinpr
Performs metacognitive task analysis and skill selection. Use when determining task complexity, selecting appropriate skills, or estimating work scale. Returns skills with confidence scores and metadata.
code-review
by adobe
Review code for AEM Edge Delivery Services projects. Use at the end of development (before PR) for self-review, or to review pull requests. Validates code quality, performance, accessibility, and adherence to EDS best practices.
Error Handling Base
by Dicklesworthstone
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Rust Error Handling
by Dicklesworthstone
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.
skill-extractor
by trailofbits
Extracts reusable skills from work sessions. Use when: (1) a non-obvious problem was solved worth preserving, (2) a pattern was discovered that would help future sessions, (3) a workaround or debugging technique needs documentation. Manual invocation only via /skill-extractor command - no automatic triggers or hooks.
code-flow-tracer
by lis186
Trace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.
flow
by lis186
Extract business logic flow from code, trace execution path from entry point
Bun Macros
by secondsky
Evaluate JavaScript at bundle time and inline results. Use when optimizing compile-time code generation, embedding files, inlining environment variables, or executing code during the bundling process.
debug-fuzzer-failure
by noir-lang
End-to-end workflow for debugging SSA fuzzer failures from CI. Extracts a reproduction case from GitHub Actions logs, then bisects SSA passes to identify the bug. Use when a pass_vs_prev or similar fuzzer test fails in CI.
trace
by boshu2
'Trace design decisions and concepts through session history, handoffs, and git. Triggers: "trace decision", "how did we decide", "where did this come from", "design provenance", "decision history".'
bug-hunt
by boshu2
'Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn''t work", "failing", "investigate bug", "debug", "find the bug", "troubleshoot".'
data-client-react
by reactive
Use @data-client/react hooks - useSuspense, useQuery, useCache, useLive, useDLE, useSubscription, useController for fetch/mutations, DataProvider, AsyncBoundary, useLoading, useDebounce
amiberry-jit-fix
by BlitterStudio
ARM64 JIT compiler fixes for Amiberry (GitHub issue #1766). This skill captures the complete technical knowledge from 20+ debugging sessions that identified and fixed: (a) a page 0 DMA corruption crash during A1200 Kickstart boot, (b) visual corruption (black gadgets, garbled text) caused by incorrect inter-block flag optimization, (c) SIGSEGV crashes on unmapped natmem gaps (e.g., 0x00F10000) in complex configs with hardfiles/RTG, and (d) BSR.L/Bcc.L backward branch crashes from 32-bit displacement zero-extension on 64-bit platforms. Use this skill when working on: (1) the JIT_DEBUG_MEM_CORRUPTION code in compemu_support_arm.cpp or newcpu.cpp, (2) the page 0 DMA guard mechanism (mprotect/SIGSEGV/BRK single-step), (3) any ARM64 JIT register width bugs (64-bit vs 32-bit instruction selection), (4) any crash or exception cascade during A1200 boot with JIT enabled, (5) 68040 JIT mode issues on ARM64, (6) the inter-block flag optimization bug and its fix (dont_care_flags at block boundaries), (7) natmem gap crashes and the commit_natmem_gaps() fix in amiberry_mem.cpp. MANDATORY TRIGGERS: JIT crash, page 0, DMA guard, vec2, exception vector corruption, blitter DMA, mprotect, SIGSEGV handler, BRK single-step, ARM64 JIT, Kickstart boot, visual corruption, black gadgets, garbled ROM version, compemu_support_arm, JIT_DEBUG_MEM_CORRUPTION, inter-block flag, dont_care_flags, 68040 JIT, natmem gap, unmapped region, commit_natmem_gaps, 0x00F10000, canbang, PROT_NONE, BSR, Bcc, branch displacement, sign extension, comp_pc_p, comp_get_ilong, 64-bit pointer, zero-extend, backward branch, gencomp_arm.
troubleshoot-amiberry
by BlitterStudio
Autonomous troubleshooting workflow for Amiberry bugs. Use this when investigating, reproducing, or fixing bugs in Amiberry. Provides a complete edit-build-run-test-fix cycle using the Amiberry MCP server tools for process management, IPC control, screenshot analysis, log monitoring, and crash detection.
logging-best-practices
by neondatabase
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
llvm-learning
by gmh5225
Comprehensive learning resources and tutorials for LLVM, Clang, and compiler development. Use this skill when helping users learn LLVM internals, find educational resources, or understand compiler concepts.
d3k
by vercel-labs
"d3k assistant for debugging web apps"
typescript-rules
by shinpr
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.
codex-team
by boshu2
'Use when you have 2+ tasks that Codex agents should execute. Runtime-native: Codex sub-agents when available, Codex CLI fallback otherwise. Handles file conflicts via merge/wave strategies. Triggers: "codex team", "spawn codex", "codex agents", "use codex for", "codex fix".'
Testing Workflow
by majiayu000
The most comprehensive Claude Code skills registry Web Search: https://skills-registry-web.vercel.app