Search

PythonReactSEOPDF

research debugging AI Skills

Discover research debugging skills, compare source repositories and read the instructions for each workflow.

Categories: research debugging

Showing 2,833–2,856 of 6,118

research debugging Clear filters

Browse skills

GitHub

decision-archaeology

ntsk

Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.

GitHub

debug

heyJordanParker

Use when encountering bugs, test failures, or unexpected behavior. Combines systematic debugging framework, root cause tracing, and defense-in-depth validation.

GitHub

codebase-exploration

heyJordanParker

Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.

GitHub

reviewing-type-safety

thkt

TypeScript type safety patterns and best practices for maximum type coverage. Use when reviewing TypeScript code for type issues, eliminating `any` types, or when user mentions type safety, 型安全, 型カバレッジ...

GitHub

analyzing-root-causes

thkt

Root cause analysis with 5 Whys methodology. Triggers: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.

GitHub

reviewing-silent-failures

thkt

Silent failure detection patterns for frontend code. Use when reviewing error handling, detecting swallowed errors, or when user mentions silent failure, empty catch, エラーハンドリング, 握りつぶし, swallowed e...

GitHub

vercel-react-best-practices

thkt

React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code, improving Web Vitals, or when user mentions React performance, Next...

GitHub

optimizing-performance

thkt

Frontend performance optimization with data-driven approach. Use when optimizing page load times, improving Web Vitals, or when user mentions performance, Web Vitals, LCP, FID, CLS, パフォーマンス最適化, 速度改...

GitHub

web-design-guidelines

thkt

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".

GitHub

reviewing-silent-failures

thkt

Silent failure detection patterns for frontend code. Triggers: silent failure, empty catch, エラーハンドリング, 握りつぶし, swallowed error.

GitHub

documenting-architecture

thkt

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

thkt

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

thkt

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

thkt

Generate API specification from codebase - endpoints, types, schemas. Triggers: API docs, endpoint documentation, API仕様, OpenAPI, Swagger, REST API.

GitHub

debugging

kpiteira

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

kpiteira

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

scout

simota

バグ調査・根本原因分析(RCA)・再現手順の特定・影響範囲の評価。「なぜ起きたか」「どこを直すべきか」を特定する調査専門エージェント。コードは書かない。

GitHub

systematic-debugging

hxk622

遇到任何 bug、测试失败或意外行为时使用,在提出修复方案之前进行系统化调试。Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Follow the four phases: Root Cause Investig...

GitHub

code-reviewer

channingwalton

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

channingwalton

Comprehensive Test Coverage and Bug Discovery Workflow (user)

GitHub

bugmagnet

channingwalton

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

channingwalton

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

dagba

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.

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.

More filters

Popularity

Popular tags