- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
Support Agent - 客服专家
by aAAaqwq
â å¯ä»¥æ¶éç¨æ·åé¦
log-focus-debug
by solidSpoon
'DashPlayer 日志聚焦调试技能。Use when developers ask to reduce noisy logs, focus on one feature log chain, add temporary focus markers (e.g. [FOCUS:token]), or clean up temporary debug logs after task completion. Triggers on: "日志太乱", "只看某个功能日志", "focus token", "withFocus", "临时日志标记", "清理调试日志".'
commit
by yonatangross
"Creates commits with conventional format and validation. Use when committing changes or generating commit messages."
opentelemetry
by bobmatnyc
"OpenTelemetry observability patterns: traces, metrics, logs, context propagation, OTLP export, Collector pipelines, and troubleshooting"
Testing Anti-Patterns
by bobmatnyc
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
go-documentation
by cxuu
Guidelines for Go documentation including doc comments, package docs, godoc formatting, runnable examples, and signal boosting. Use when writing or reviewing documentation for Go packages, types, functions, or methods.
elixir-essentials
by j-morgan6
MANDATORY for ALL Elixir code changes. Invoke before writing any .ex or .exs file.
phoenix-liveview-essentials
by j-morgan6
MANDATORY for ALL LiveView work. Invoke before writing LiveView modules or .heex templates.
perl-development
by Jamie-BitFlight
This skill should be used when the user asks to "write a Perl script", "create Perl code", "modern Perl best practices", "Perl 5.30+", "use strict warnings autodie", or mentions Perl pragmas, subroutines, error handling, or scripting patterns. Provides comprehensive Perl 5.30+ development guidance.
bash-development
by Jamie-BitFlight
This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.
validation-protocol
by Jamie-BitFlight
Scientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, or implementation is complete. Enforces create-broken-state — define-success-criteria — apply-fix — verify-outcome workflow. Success equals observing intended behavior, not absence of errors.
commitlint
by Jamie-BitFlight
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
conventional-commits
by Jamie-BitFlight
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.
Bun HTTP Server
by secondsky
Use when building HTTP servers with Bun.serve, handling requests/responses, implementing routing, creating REST APIs, or configuring fetch handlers.
react-server-components
by ryoppippi
Review React code for proper Server/Client Component boundaries based on Next.js and React documentation. Identifies misplaced 'use client' directives and suggests optimal component splitting.
ask-claude
by ryoppippi
Consult Claude Code for a second opinion on implementation plans, code reviews, or problem-solving. Use when you want an independent perspective from a different AI agent before making significant decisions.
test-specialist
by ailabs-393
This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.
test-specialist
by ailabs-393
This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.
playwright-debugging
by ed3dai
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
Palette
by simota
ã¦ã¼ã¶ããªãã£æ¹åãã¤ã³ã¿ã©ã¯ã·ã§ã³å質åä¸ãèªç¥è² è·è»½æ¸ããã£ã¼ãããã¯è¨è¨ãa11y対å¿ãUXã®ä½¿ãåæãè¯ãããããæä½æãæ¹åãããæã«ä½¿ç¨ã
best-practices
by skillcreatorai
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
odoo-upgrade
by ahmed-lakosha
"Comprehensive Odoo ERP upgrade assistant for migrating modules between Odoo versions (14-19). Handles XML views, Python API changes, JavaScript/OWL components, theme SCSS variables, manifest updates, security implementations, and database migrations. Use when user asks to upgrade Odoo modules, fix version compatibility issues, migrate themes between versions, or resolve Odoo 17/18/19 migration errors. Specializes in frontend RPC service migrations, view XML transformations, theme variable restructuring, and portal template XPath fixes."
diagnose-performance
by melodic-software
Run comprehensive Claude Code performance diagnostics - analyzes storage, API status, and known issues
debug-os-worker
by iterate
Debug failures in the Cloudflare os worker using the Cloudflare MCP server (events, keys, values, and targeted queries). Use when diagnosing 500s, missing logs, daemon/control-plane issues, or request-level regressions in production.