GitHub
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Skills IA lifestyle debugging
Découvrez les skills lifestyle debugging, comparez leurs dépôts et consultez leurs instructions.
Catégories: lifestyle debugging
lifestyle debugging Effacer les filtres
Explorer
GitHub
reviewing-silent-failures
Silent failure detection patterns for frontend code. Triggers: silent failure, empty catch, エラーハンドリング, 握りつぶし, swallowed error.
GitHub
documenting-architecture
Generate architecture overview documentation from codebase analysis. Uses tree-sitter-analyzer for precise code structure extraction. Use when documenting project structure, creating architecture diagrams, or w...
GitHub
documenting-architecture
Generate architecture overview documentation from codebase analysis. Uses tree-sitter-analyzer for precise code structure extraction. Triggers: architecture overview, project structure, module diagram.
GitHub
analyzing-root-causes
Root cause analysis with 5 Whys methodology. Use when investigating bugs, analyzing failures, or when user mentions root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
GitHub
documenting-apis
Generate API specification from codebase - endpoints, types, schemas. Triggers: API docs, endpoint documentation, API仕様, OpenAPI, Swagger, REST API.
GitHub
debugging
Use when troubleshooting host service connectivity, debugging data loading issues, investigating progress tracking problems, diagnosing environment or configuration issues, or checking Grafana dashboards.
GitHub
observability
Use when diagnosing operation failures, stuck or slow operations, querying Jaeger traces, working with Grafana dashboards, debugging distributed system issues, or investigating worker selection and service comm...
GitHub
debug-logs
Structured debugging workflow with log server capture and analysis
GitHub
scout
バグ調査・根本原因分析（RCA）・再現手順の特定・影響範囲の評価。「なぜ起きたか」「どこを直すべきか」を特定する調査専門エージェント。コードは書かない。
GitHub
systematic-debugging
遇到任何 bug、测试失败或意外行为时使用，在提出修复方案之前进行系统化调试。Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Follow the four phases: Root Cause Investig...
GitHub
code-reviewer
Review code for best practices, security, performance, and potential issues. Use when reviewing code, checking pull requests, analysing code quality, or when asked to critique implementation.
GitHub
bugmagnet
Comprehensive Test Coverage and Bug Discovery Workflow (user)
GitHub
bugmagnet
Discover edge cases and test coverage gaps through systematic analysis. Use when analysing test coverage, finding bugs, hunting for edge cases, or when code-reviewer identifies test gaps.
GitHub
code-reviewer
Autonomous code review for best practices, security, performance, and potential issues. Runs in isolation with read-only tools using Opus model. Use when reviewing code, checking PRs, or analysing code quality.
GitHub
swift-concurrency-expert
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
GitHub
code-review
Reviews code and suggests improvements. Use when asked to review code or propose refactors.
GitHub
codebase-search
Semantic code search by meaning. Use codebase_peek to find WHERE code is (saves tokens), codebase_search to see actual code. For exact identifiers, use grep instead.
GitHub
sentry
Queries Sentry for issues, events, traces, and error analysis. Use when debugging production errors, searching issues, analyzing traces, or getting AI root cause analysis with Seer.
GitHub
analyze-project
Use when starting work on an unfamiliar project or needing to understand a codebase - performs comprehensive analysis discovering architecture, patterns, dependencies, testing coverage, and improvement opportun...
GitHub
research-capture
Captures research insights, decisions, and learnings during development. Use after completing spikes, making architectural decisions, or discovering important patterns. Prompts for context and rationale, stores...
GitHub
systematic-debugging
Four-phase debugging: root cause → patterns → hypothesis → implement. For complex bugs, test failures, multi-component issues. NOT for obvious syntax errors.
GitHub
bug-reporter
Capture bug context, generate reports, and optionally create GitHub issues or share patterns
GitHub
pop-benchmark-runner
Orchestrates benchmark execution comparing PopKit vs baseline Claude Code
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é.