debug-helper
Systematic debugging approach for identifying and fixing issues. Use when debugging, troubleshooting errors, or asking about bugs and problems.
Découvrez les skills development debugging, comparez leurs dépôts et consultez leurs instructions.
Systematic debugging approach for identifying and fixing issues. Use when debugging, troubleshooting errors, or asking about bugs and problems.
Provides systematic code review with focus on quality, security, and best practices. Use when reviewing code, doing PR reviews, or asking for code feedback.
Guidelines and checklist for thorough code review.
Explore codebase, understand architecture, find how things work. Navigate unfamiliar repositories, discover code structure, find where functionality lives by intent rather than exact text. NOT for debugging fai...
Debug errors, trace bugs, find root causes. Investigate why code fails, trace execution paths, troubleshoot unexpected behavior, find why functions return wrong values. NOT for exploring unfamiliar code (use ex...
Runs Playwright E2E tests with smart targeting by app and feature, supports multiple environments (local/staging/production), and can generate new E2E test files. This skill should be used when running E2E test...
Verifies system health across all apps, edge functions, and database connectivity. This skill should be used for quick deployment verification, debugging service issues, daily operations checks, or before/after...
Uses ast-grep to find patterns and analyze code for refactoring. Use when planning refactors, finding deprecated API usage, migrating code, or analyzing code quality before changes. For simple code search, use...
Claudeを使った多角的コードレビュー。セキュリティ、パフォーマンス、保守性、設計の4観点で並列分析。 Use for: "レビューして", "コードレビュー", "多角的に見て", "4観点でレビュー"
Professional code review for quality, security, and best practices. Use when reviewing pull requests, code changes, or when asked to review code quality.
Semantic code search using Mantic. Use when exploring codebases, finding feature implementations, understanding component functionality, locating definitions/references, or mapping architectural patterns. Use M...
Use when working with Ruby metaprogramming features including dynamic method definition, method_missing, class_eval, define_method, and reflection.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Debug React component issues including TypeScript types, props, state management, hooks, and rendering problems. Use when troubleshooting component not rendering, prop errors, state not updating, hook issues, o...
Self-diagnostic debugging - Agent decides diagnostic approach. Auto-activates on "bug", "error", "debug", "不work", "壞掉" keywords. AMP principle: Think > Follow - Agent writes own debug tools.
Updates Aaron's Core Memory (CLAUDE.md) with session notes, project status, and development patterns
Information about Probitas framework. Use when asked "what is Probitas", explaining its purpose, features, or comparing with other test frameworks.
Analyze logs, reproduce issues, and create a fix plan.
Reverse-engineer specifications from source code
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
Analyze web interfaces for UX issues, accessibility compliance (WCAG 2.1), color contrast, typography hierarchy, responsive design, and Core Web Vitals. Returns actionable improvements with code examples.
Systematic identification of race conditions, concurrency bugs, and thread-safety issues across codebases. Use when asked to find race conditions, audit concurrent code, debug non-deterministic behavior, review...
Perform comprehensive code audits on repositories or directories. Use when asked to audit code, review a codebase, analyze code quality, find bugs, check for security issues, review architecture, check SOLID/DR...
Provide architecture guidance, module boundaries, data flow, API design, and trade-off analysis. Use when asked for system design, refactor plans, or architecture docs.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.