Discover data ai debugging skills, compare source repositories and read the instructions for each workflow.
Systematic debugging methodology emphasizing root cause analysis over quick fixes. Use when debugging complex issues, investigating production failures, or avoiding symptom-based patches in favor of understandi...
Test quality inspection framework for reviewing test coverage, identifying gaps, and ensuring comprehensive validation. Use when reviewing test suites, performing QA inspections, or establishing testing quality...
Rust code review patterns from corrode.dev (16 articles)
Full-stack performance analysis, optimization patterns, monitoring strategies, React 19 concurrent features, and bundle analysis for 2025+ development
React 19 best practices, hooks, state management and data fetching. Use when writing components, hooks, managing state, handling async operations or reviewing React code.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
ALWAYS check before working with Linear issues. Guide for Linear-related skills for ticket management and debugging workflows.
Reviews code for best practices, bugs, security issues, and provides improvement suggestions
Trace bugs backward to their origin, not just symptoms
Structured approach to finding and fixing bugs
Use this skill when asked to "validate plugin", "check plugin structure", "verify plugin", "audit plugin", "is my plugin correct", "plugin issues", or when troubleshooting plugin problems.
Autonomously explore unfamiliar codebases using Julie's code intelligence. Use semantic search, symbol navigation, and call path tracing to understand architecture without reading entire files. Activates when u...
Use Julie's semantic search capabilities for conceptual code understanding. Activates when searching for concepts, cross-language patterns, business logic, or exploring unfamiliar code. Combines text and semant...
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. Th...
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-driv...
Deep codebase analysis to generate 9 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical impl...
Generate a visual spec-to-code coverage map showing which code files are covered by which specifications. Creates ASCII diagrams, reverse indexes, and coverage statistics. Use after implementation or during cle...
Interactive conversation to resolve [NEEDS CLARIFICATION] markers using /speckit.clarify command. Claude asks questions about missing features, UX/UI details, behavior, and priorities. Updates specs in .specify...
Complete reference for Claude Code's memory management system including all file types, locations, import syntax, and best practices. Use when planning or managing CLAUDE.md and related memory files.
30 pragmatic rules for production JavaScript covering async operations, V8 optimization, memory management, testing, error handling, and performance. Use when writing JavaScript, optimizing performance, handlin...
Perform code review using CodeRabbit. Must use this skill if instructed to perform a CodeRabbit review.
Analyzes MVP codebases and recommends prioritized next steps for product development. Use when the user asks "what should I build next?", "how do I improve my MVP?", "what features should I add?", or needs guid...
Hidden automatic debugging when something breaks - user sees simple question or "fixing..." not stack traces or technical errors
Identify performance bottlenecks systematically. Measure before optimizing.
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.