systematic-debugging
Systematic 4-phase debugging process for finding root causes
Discover research debugging skills, compare source repositories and read the instructions for each workflow.
Systematic 4-phase debugging process for finding root causes
Review Flipper Zero firmware code changes for Momentum-specific patterns, security, and compatibility when analyzing firmware modifications or pull requests.
Generate blameless postmortem with root cause analysis
Diagnose and fix bugs with architecture-aware analysis and diagnostic-first approach
Code review mode - comprehensive review with security, performance, and maintainability focus
Analyze test coverage gaps and report findings
Guide systematic debugging through hypothesis generation and verification
Analyzes design docs and existing projects to create detailed, actionable implementation plans for Claude Code. Use when the user asks to create an implementation plan, analyze a feature, or break down tasks.
Patterns for showing thinking process and execution chain. Every step visible, every decision traceable.
Quick project reconnaissance and health check via @geepers_scout - identifies issues, quick wins, and improvement opportunities.
Deep Python knowledge for code reviews. Provides detailed guidance on iterables, data structures, standard library, validation, testing, concurrency, APIs, and security.
AI-powered QA verification using Playwright MCP for visual E2E testing. Use when (1) Verifying UI changes after code modifications, (2) Testing user workflows end-to-end, (3) Checking for visual regressions, (4...
React performance optimization guidelines focused on Tanstack Start applications. Use when writing, reviewing, or refactoring React code with Tanstack Start, Tanstack Query, and Tanstack Router. Triggers on Rea...
Expert integration for the Serena MCP Server - a powerful coding agent toolkit providing IDE-like semantic code understanding to LLMs. This skill should be used when working with codebases through Serena tools,...
Provides comprehensive Python code review with focus on quality, bugs, security, and best practices. Use when reviewing Python code, functions, or modules for quality assessment.
Performance and scalability analysis specialist. Identifies algorithmic inefficiencies, N+1 queries, memory leaks, and concurrency issues. Use when reviewing loops, database queries, file I/O, or high-concurren...
Deep codebase context analysis like Greptile. Analyzes blast radius of changes, dependency graphs, and architectural consistency. Use when reviewing changes to core utilities, shared libraries, or database mode...
Zero-trust security analysis like Cursor BugBot. Focuses exclusively on finding exploitable vulnerabilities with high confidence (>95%). Use when reviewing files that handle input parsing, database queries, aut...
Review test coverage and quality. Analyzes unit tests, integration tests, determinism, and test design. Use when reviewing test files or code that should have tests.
Review database operations, migrations, and data persistence. Analyzes query safety, migration rollback, transaction boundaries, and data integrity. Use when reviewing migrations, models, repositories, or datab...
Review logging, metrics, tracing, and alerting. Ensures systems are observable, debuggable, and operable. Use when reviewing code that adds logging, metrics, or monitoring.
Analyze code for logic bugs, error handling issues, and edge cases. Detects off-by-one errors, null handling, race conditions, and incorrect error paths. Use when reviewing core business logic or complex algori...
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automa...
Enforce Claude Compass development standards and best practices. This skill should be used when writing or modifying code in the Claude Compass repository, including parsers, database migrations, graph builders...
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.