অনুসন্ধান সক্রিয়

স্কিল খুঁজুন

আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।

জনপ্রিয় অনুসন্ধান
ফলাফল
53,183
এই অনুসন্ধানের সাথে মিলে যাওয়া স্কিল
পৃষ্ঠা
2617
2660টির মধ্যে
কীওয়ার্ড
ai
নাম, ট্যাগ বা বিবরণ দিয়ে খুঁজুন
debugging
0

observability

Telemetry, metrics, tracing, and observability for Elixir/BEAM applications

layeddie
layeddie
tools
open
debugging
0

debugger

Use when the root cause is unclear. Trace the failure back through the call stack and isolate the first bad state.

rozwer
rozwer
tools
open
debugging
0

debug-like-expert

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.

aaronvstory
aaronvstory
tools
open
debugging
0

rl-debugging

Systematic RL debugging - diagnose learning failures, common bugs, diagnosis trees

tachyon-beep
tachyon-beep
tools
open
debugging
0

chrome-devtools-automation

Control Chrome browser through MCP for testing, debugging, network analysis, and performance profiling. Use when testing web apps, measuring Core Web Vitals, analyzing network requests, debugging console errors, or when the user mentions Chrome DevTools, performance traces, or browser automation.

amo-tech-ai
amo-tech-ai
tools
open
debugging
0

pm-08-performance

Analyse throughput, case duration, and activity sojourn times from the filtered log.

Wattysaid
Wattysaid
tools
open
debugging
0

analyze

Invoke IMMEDIATELY via brain-hooks when user requests codebase analysis, architecture review, security assessment, or quality evaluation. Do NOT explore first - the command orchestrates exploration.

loriensleafs
loriensleafs
tools
open
debugging
0

optimization-techniques

Performance optimization strategies. Use ONLY after profiling identifies bottlenecks.

IvanTorresEdge
IvanTorresEdge
tools
open
debugging
0

dev-debug-cpp

C++ debugging for segfaults, memory corruption, threading issues, and linker/ABI problems. Use when encountering crashes (exit code 139/SIGSEGV), memory leaks, data races, undefined behavior, or when debugging native Node.js addons, FFmpeg integrations, or any C++ code that crashes mysteriously.

pproenca
pproenca
tools
open
debugging
0

debug

Use when encountering bugs, test failures, or unexpected behavior - find root cause before fixing

TKontu
TKontu
tools
open
debugging
0

spec-miner

Reverse-engineer specifications from undocumented code. Use for legacy systems or creating documentation from implementations.

kamushadenes
kamushadenes
tools
open
debugging
0

code-review-repo

Review local codebase for bugs and CLAUDE.md compliance using multi-agent analysis

blueraai
blueraai
tools
open
debugging
0

profiling-with-cpu-sampler

Time-based sampling profiler showing WHERE execution time is spent (wall-clock time, not frequency). Provides histogram with self/total time, compilation tiers (T0/T1/T2), and flame graphs. Use as FIRST step to identify hot functions consuming most time. Low overhead, suitable for longer runs. Pair with tracing-execution-counts to understand time-per-execution vs execution frequency.

antonykamp
antonykamp
tools
open
debugging
0

oe-backend-prod-hardening

Production hardening review for the OpenEvent backend. Use when scanning for LLM smells, noisy prints, swallowed exceptions, dev-only defaults, fallback diagnostic leakage, and inconsistent error/logging patterns; produce a prioritized, PR-sized cleanup plan.

shami-ah
shami-ah
tools
open
debugging
0

systematic-debugging

体系的デバッグスキル。根本原因調査を先に行い、修正は後に行う規律あるアプローチ。

HaRu-LLC
HaRu-LLC
tools
open
debugging
0

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior in C#/.NET code before proposing fixes; applies to gRPC services, EF Core queries, async operations, and build failures

donellmccoy
donellmccoy
tools
open
debugging
0

ios-sim-interrogate

iOS Simulator interrogation: simctl screenshots/video, Web Inspector for web content, Instruments for native behaviors.

jscraik
jscraik
tools
open
debugging
0

netgraph-dev

NetGraph contributor development workflow. Use when: setting up dev environment, running tests or lint, fixing CI failures, running performance benchmarks, troubleshooting venv issues, or asking about make targets. For running scenarios and interpreting results, use netgraph-dsl instead.

networmix
networmix
tools
open
debugging
0

systematic-debugging

Four-phase structured debugging methodology. Use when (1) tests fail unexpectedly, (2) functions produce wrong values, (3) systems show anomalous results, (4) unexpected errors appear, (5) performance regresses, (6) multiple quick fixes have already failed. Enforces root cause investigation before any fix attempt.

nandkapadia
nandkapadia
tools
open
আগের
পৃষ্ঠা 2617 / 2660
পরের