debugging
3
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, 対症療法.
thkt
tools
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
debugging
3
palace-python-expert
Expert in Python development with focus on best practices, testing, and modern Python features
Zorlin
tools
debugging
3
ida-domain-scripting
Write and execute Python scripts using the IDA Domain API for reverse engineering. Analyze binaries, extract functions, strings, cross-references, decompile code, work with IDA Pro databases (.i64/.idb). Use when user wants to analyze binaries, reverse engineer executables, or automate IDA Pro tasks.
HexRaysSA
tools
debugging
3
binary-analysis-and-reverse-engineering
Systematic approach to analyzing compiled binaries, understanding program behavior, and identifying vulnerabilities without source code access
macaugh
tools
debuggingmarketplace
2
detection-engineering
Expert Detection Engineer assistant for creating and testing D&R rules in LimaCharlie. Guides through understanding threats, researching event data (Schema, LCQL, Timeline), generating detection logic, testing rules against sample and historical data, and deploying validated rules. Use for building detections, writing D&R rules, testing detection logic, or when user wants to detect specific behaviors or threats.
refractionPOINT
tools
debugging
2
product-challenger
A skeptical product advisor that challenges requirements and feature designs using first-principles thinking. Use when user wants to review requirements, analyze features, validate product decisions, evaluate PRDs, or question if a feature is worth building. Helps identify fake requirements through evidence-based challenges, searching real user feedback across multiple channels, and analyzing code structure to assess implementation cost.
guangtouwangba
tools
debugging
2
performance-analyst
RAN performance analysis with bottleneck detection, cognitive consciousness, and temporal reasoning for deep performance insights. Use when analyzing RAN performance, detecting bottlenecks, optimizing network efficiency, or implementing cognitive performance monitoring.
ricable
tools
debugging
2
performance-engineering
Domain specialist for performance optimization, profiling, caching, and resource management. Scope: profiling tools, caching strategies, load testing, observability, N+1 query detection, algorithm complexity analysis, resource leak detection, connection pooling, query optimization, memory leaks, file handle leaks, connection leaks. Excludes: code architecture, security operations, database design, infrastructure. Triggers: "performance", "slow", "optimization", "profiling", "caching", "load test", "bottleneck", "resource leak", "N+1", "memory leak", "complexity".
warpcode
tools
debugging
2
performance-profiler
Profile application performance, identify bottlenecks, and optimize for speed
eddiebe147
tools
debugging
2
commit-postmortem-generator
This skill should be used when the user asks to "analyze fix commits and generate postmortems", "create postmortems from git history", or "summarize bug fixes into postmortem reports".
tizee
tools
debugging
2
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 opportunities. Do NOT use on projects you already know well or for targeted questions about specific files - use direct exploration instead for focused queries.
jrc1883
tools
debugging
2
transparency
Patterns for showing thinking process and execution chain. Every step visible, every decision traceable.
duyet
tools
debugging
2
code-review-checklist
Comprehensive checklist and best practices for effective code reviews that catch bugs and improve code quality
cyperx84
tools
debugging
2
researching-codebase
This skill should be used when the user asks to "research the codebase", "understand how X works", "explore the code", "gather context", "investigate the implementation", "analyze the architecture", or invokes the rpikit:research command. Provides methodology for thorough interrogation and codebase exploration before planning or implementation.
bostonaholic
tools
debugging
2
exploring-codebase
Performs in-depth codebase exploration at the start of a coding session. Builds comprehensive understanding of project structure, architecture, key components, and patterns. Use when starting a new session, when asked to understand or explore the codebase, when asked "what does this project do", when exploring unfamiliar code, or when the user asks about project structure or architecture.
Sun-Lab-NBB
tools
debugging
2
coding-workflow
Best practices for coding, debugging, and refactoring. Use when reviewing code, debugging issues, refactoring, or establishing coding patterns.
az9713
tools
debugging
2
bug-analysis
Analyzes software bugs including root cause identification, severity assessment, impact analysis, reproduction steps validation, and fix recommendations. Performs bug triage, categorization, duplicate detection, and regression analysis. Use when investigating bugs, analyzing crash reports, triaging issues, debugging problems, reviewing error logs, or when users mention "analyze bug", "investigate issue", "debug problem", "bug report", "crash analysis", "root cause analysis", or "fix recommendation".
DauQuangThanh
tools
debugging
2
gap-analysis
Route-aware gap analysis. For Brownfield - uses /speckit.analyze to compare specs against implementation. For Greenfield - validates spec completeness and asks about target tech stack for new implementation. This is Step 4 of 6 in the reverse engineering process.
jschulte
tools
debugging
2
code-analysis
Structured codebase analysis for understanding architecture, patterns, and dependencies. Use when onboarding to a codebase, planning changes, or assessing impact.
korallis
tools
debugging
2
moai-change-logger
Comprehensive change tracking and audit logging system that monitors file modifications, code changes, and project evolution. Use when tracking project history, maintaining audit trails, analyzing development patterns, or when detailed change documentation is required for compliance and team collaboration.. Enhanced with Context7 MCP for up-to-date documentation.
AJBcoding
tools
debugging
2
performance-optimizer
Expert in React performance optimization, code splitting, lazy loading, memoization, bundle analysis, Core Web Vitals, Lighthouse audits, and runtime performance profiling
deve1993
tools
debugging
2
analyze
Perform initial analysis of a codebase - detect tech stack, directory structure, and completeness. This is Step 1 of the 6-step reverse engineering process that transforms incomplete applications into spec-driven codebases. Automatically detects programming languages, frameworks, architecture patterns, and generates comprehensive analysis-report.md. Use when starting reverse engineering on any codebase.
jschulte
tools
debugging
2
debugging-memory
This skill should be used when the user asks to "debug this", "fix this bug", "why is this failing", "investigate error", "getting an error", "exception thrown", "crash", "not working", "what's causing this", "root cause", "diagnose this issue", or describes any software bug or error. Also activates when spawning subagents for debugging tasks, using Task tool for bug investigation, or coordinating multiple agents on a debugging problem. Provides memory-first debugging workflow that checks past incidents before investigating.
tyroneross
tools