Debugging
Find and fix bugs, error analysis
bundle-import-auditor
by handxr
Audit JavaScript/TypeScript imports for bundle size bloat, heavy dependencies with lighter alternatives, wildcard imports that break tree-shaking, barrel file re-exports, duplicate imports, code-splitting opportunities, and import hygiene issues. Use when reviewing frontend bundle size, debugging slow page loads, auditing import patterns, or when a user asks to check their imports, find heavy dependencies, optimize bundle size, detect tree-shaking blockers, or clean up import statements. Triggers on tasks involving .js/.jsx/.ts/.tsx/.mjs/.mts files with ES module imports or require() calls.
conventional-commits
by devinschumacher
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages.
task-capture
by qingchunwuhui
任务采集助手 - 纯粹的任务执行记录工具，专注于实时采集，零摩擦启动。 遵循"采集与加工分离"原则：启动时只记录，不复盘。 Triggers: /task-capture, /capture, /记录
commit
by myuon
Conventional Commitsに従ってgit commitを実行
vm-bug-hunter
by zeal422
Detects actual programming errors including syntax, runtime, logical, semantic, linker, resource, security, type, and index/attribute errors. Auto-detects language and focuses on legitimate bugs, not hallucinations.
qodo-pr-resolver
by ilchemla
Resolve Qodo PR review comments through analyze-confirm-execute workflow with severity-based prioritization. Analyzes comment validity, detects CI failures, confirms response approach with user, executes code changes, runs tests, and resolves threads. Use when responding to Qodo PR review comments, addressing Qodo feedback, resolving review issues, or managing Qodo review threads.
debug
by iulspop
Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.
opus-design-question
by ddaanet
Consult Opus for design and architectural decisions. REQUIRED instead of AskUserQuestion. Triggers on approach choices (A vs B), trade-off analysis, pattern selection, or structural decisions — use this skill to consult Opus instead of asking the user. Only ask the user for subjective preferences, business logic, scope changes, or unclear requirements.
test-driven-development
by Jackiexiao
（中文）Use when implementing any feature or bugfix, before writing implementation code
fe-debug
by ingpdw
React/Next.js 앱의 에러를 진단하고 디버깅하는 스킬. Error Boundary, 에러 추적, 일반적인 React/Next.js 에러 해결, 런타임 디버깅 등. "디버깅", "debug", "에러", "error", "버그", "안돼", "오류", "트러블슈팅" 등의 요청 시 사용.
data-engineering-observability
by legout
"Observability and monitoring for data pipelines using OpenTelemetry (traces) and Prometheus (metrics). Covers instrumentation, dashboards, and alerting."
bf-lead-plan
by khaki4
Tech Spec을 분석하여 Epic/Story 구조를 생성하고, Story 5개 이상일 때 병렬로 Story 문서를 작성한다. Distribute 조율 패턴.
go-error-handling
by imrenagi
Best practices for error handling in Go applications, including error wrapping, domain errors, sentinel vs typed errors, and gRPC error mapping.
error-recovery
by BaxterCooper
Use when tasks fail due to transient errors. Provides structured retry strategies and graceful degradation patterns. Invoke on network errors, rate limits, or intermittent failures.
claude-framework
by vineethsoma
CLAUDE Framework coding standards for code quality, naming conventions, error handling, security, testing, database, and logging
rails-active-job
by shivamsinghchahar
Master Active Job framework for asynchronous background job processing. Use when building background workers, handling async operations, managing job queues, scheduling recurring tasks, or processing long-running operations. Covers job definition, Solid Queue backend, error handling, and advanced patterns.
sveltekit
by lcaparros
Expert guidance for building modern, performant web applications with SvelteKit.
aeo-failure-patterns
by ivzc07
Recognize common errors and apply known fixes automatically. Hybrid: core patterns + project-specific learning.
useuser
by willwillems
Ask humans questions via native macOS dialogs and notifications. Use when you need clarification, confirmation, or direct input from the user through system-level dialogs rather than chat. Supports text input, multiple choice, yes/no confirmation, information display, and system notifications.
model-router
by oyi77
Intelligent model routing via subagents - automatically spawn the right model for each task complexity
quick-brainstorm
by Hccake
Lightweight brainstorming for bug fixes, small features, or code improvements that need clarification before implementation. Triggers deep questioning to ensure accurate output. Use when user asks to fix a bug, add a small feature, refactor code, or make targeted improvements — and the scope is small enough that a full brainstorm session is unnecessary. Do NOT use for large-scale architecture decisions or greenfield projects.
react-doctor
by Jackiexiao
Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.
hypothesis-tracker
by biruk741
Manages debugging session state and tracks hypotheses. Prevents hypothesis cycles and maintains investigation history.
mutation-testing
by Envy-7z
Finds weak or missing tests by analyzing if code changes would be caught. Use when verifying test effectiveness, strengthening test suites, or validating TDD workflows.