Discover data ai debugging skills, compare source repositories and read the instructions for each workflow.
Audit backend services for security, reliability, performance, and operability issues. Use when reviewing APIs, microservices, workers, or backend code changes. Triggers on "audit backend", "security review", "...
Audit frontend code for security, UX regressions, performance, and accessibility issues. Use when reviewing React, Next.js, Vue, Svelte, or any frontend code changes. Triggers on "audit frontend", "review UI",...
Review architectural changes for coupling, blast radius, and long-term impact. Use when evaluating system design changes, cross-service dependencies, API changes, or infrastructure modifications. Triggers on "a...
Assess whether tests actually protect the system from regressions. Use when reviewing test coverage, evaluating test quality, or identifying missing tests. Triggers on "test review", "test quality", "coverage g...
Next.js/React performans analizi ve optimizasyonu. Bundle size analizi, lazy loading, memoization, re-render önleme, Core Web Vitals iyileştirme, API response caching ve database query optimizasyonu. Activate:...
Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, and Python. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, co...
Comprehensive code review and analysis. AUTO-TRIGGERS when user asks to review, refactor, debug, critique, or analyze code.
This skill should be used when the user asks about "interpreting ctx-monitor traces", "understanding execution logs", "reading trace files", "what do ctx-monitor events mean", "debugging trace output", or needs...
Fast environment briefing for agents and subagents. Use at session start to learn OS/shell, container/WSL/VM status, git repo + upstream + dirty state, Python venv status/locations, markdown folders to read, an...
comprehensive project analysis identifying issues, missing documentation, and improvement opportunities. use when reviewing codebase health, onboarding to existing project, or conducting code quality assessment...
Guide for debugging failing GitHub Actions workflows. Use this when asked to debug failing GitHub Actions workflows.
Real-time X ecosystem insights — Grok's unique advantage
Comprehensive forensic analysis skill for enterprise codebases across Azure, Dynamics 365, C#, SAP, Mulesoft, Power Platform, and more. Covers security, performance, architecture, and compliance in multi-langua...
Find, triage, and fix bugs with or without user input. Autonomously scan codebases, produce an issues list, implement a fix, create a fix branch, commit via semantic-commit, and open a PR with gh.
Analyze test coverage, identify gaps, suggest strategic test cases. Use when writing features, after bug fixes, or during test reviews. Ensures comprehensive coverage without over-testing.
Analyze test suites for speed bottlenecks, redundancy, and DRY violations. Use when tests are slow, duplicated, or need refactoring.
Perform exploratory QA testing on web applications using Playwright. Navigate flows, analyze pages, find issues, and generate actionable reports with evidence.
Debug API 500 errors and unexpected responses. Use when mobile apps get server errors, when API returns wrong data, or when investigating failed requests. Checks server logs, common error patterns, and Prisma q...
Debug web app by capturing and analyzing console errors using Chrome DevTools MCP
Systematic debugging approach for identifying and fixing issues. Use when debugging, troubleshooting errors, or asking about bugs and problems.
Provides systematic code review with focus on quality, security, and best practices. Use when reviewing code, doing PR reviews, or asking for code feedback.
Guidelines and checklist for thorough code review.
Explore codebase, understand architecture, find how things work. Navigate unfamiliar repositories, discover code structure, find where functionality lives by intent rather than exact text. NOT for debugging fai...
Debug errors, trace bugs, find root causes. Investigate why code fails, trace execution paths, troubleshoot unexpected behavior, find why functions return wrong values. NOT for exploring unfamiliar code (use ex...
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.