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.
Discover development debugging skills, compare source repositories and read the instructions for each workflow.
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.
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...
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...
Four-phase debugging: root cause → patterns → hypothesis → implement. For complex bugs, test failures, multi-component issues. NOT for obvious syntax errors.
Capture bug context, generate reports, and optionally create GitHub issues or share patterns
Orchestrates benchmark execution comparing PopKit vs baseline Claude Code
Project feasibility analysis toolkit. Evaluate technical feasibility, resource requirements, market viability, risk factors, and implementation challenges for informed go/no-go decisions on software projects.
Component specification toolkit for breaking software projects into discrete, buildable blocks. Create detailed specifications with interfaces, dependencies, test criteria, and effort estimates for Claude Code...
Detect and analyze FSD layer structure in a project
Universal pattern detector - learns from ANY codebase through sample analysis
Quick reference cheatsheets for Kailash SDK patterns, nodes, workflows, and best practices. Use when asking about 'quick tips', 'cheat sheet', 'quick reference', 'common mistakes', 'node selection', 'workflow p...
Auto-review Go code for 100+ common mistakes when analyzing .go files, discussing Go patterns, or reviewing PRs with Go code. Checks error handling, concurrency, interfaces, performance, testing, and stdlib usa...
Profile CPU, memory, and I/O usage to identify bottlenecks, analyze execution traces, and diagnose performance issues
Measure and improve test coverage by identifying untested code paths and prioritizing high-risk areas for testing
Systematically reproduce, diagnose, and analyze bugs to determine root cause, assess severity, and plan fix strategy
Apply structured logging best practices using Pino for Node.js applications: JSON output, log levels, context, redaction, correlation IDs, and centralization. Use when implementing logging, reviewing log statem...
Codebase mapping and documentation using parallel AI subagents. Invoke for: map this codebase, document architecture, understand codebase, onboarding to new project, create CODEBASE_MAP.md, generate architectur...
Optimize SwiftUI and Swift app performance with Instruments profiling, lazy loading, memory management, and view optimization. Use when diagnosing slow UI, fixing memory leaks, optimizing scroll performance, or...
Technical research methodology using Context7, Exa, and Sequential Thinking for documentation, best practices, and complex investigations.
Codebase exploration techniques for rapid discovery, architecture analysis, pattern detection, and dependency mapping.
React performance optimization - memo, useMemo, useCallback, lazy loading, virtualization. Use when optimizing React app performance.
Code quality validation with linters, SOLID principles, error detection, and architecture compliance across all languages.
Evaluate TappsCodingAgents framework effectiveness and provide continuous improvement recommendations. Use for analyzing usage patterns, workflow adherence, and code quality metrics.
Investigate and fix bugs. Use when debugging errors, analyzing stack traces, or tracing code execution. Includes Context7 error pattern knowledge and library documentation lookup.
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.