root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source o...
Découvrez les skills data ai debugging, comparez leurs dépôts et consultez leurs instructions.
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source o...
Use this skill BEFORE using writing any Clojure code. It teaches how to use the Clojure REPL (via brepl) so you can test code, check if edited files compile, verify function behavior, or interact with a running...
REPL debugging tool for capturing and inspecting local scope at runtime. Use when debugging functions, investigating test failures, understanding intermediate values, or when you need to recreate the runtime co...
Expert skill for Next.js 16 frontend development with React, TypeScript, and TailwindCSS. Use when building UI components, implementing hooks, or debugging frontend issues.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Expert skill for running and managing Project Aegis adversarial red-teaming campaigns. Use when working with Aegis simulations, prompt transformations, or jailbreak testing.
Expert skill for testing and debugging the FastAPI backend. Use when working with API endpoints, database operations, authentication, or middleware troubleshooting.
Execute when you see "[MEMORY_KEEPER]" in hook output. Follow the numbered steps exactly to save session memory.
Audit and map a codebase to understand structure, dependencies, and risks. Use when the user asks to audit a repo, understand architecture, or assess codebase quality or health.
Audit or critique a plan for feasibility, risks, missing steps, and test coverage. Use when the user asks to review, audit, or critique a plan or process.
This skill should be used for multi-perspective analysis through parallel copilot sessions. Triggers include "analyze from multiple angles", "what are the gaps/patterns/friction", "explore before deciding", pre...
Analyze developer experience friction and codebase bottlenecks. Triggers include "analyze friction", "find bottlenecks", "why is development slow", "audit codebase complexity", or "DX review".
Standardized, hypothesis-driven debug investigation workflow for unexpected behavior, regressions, incidents, flaky tests, or production issues. Use to plan instrumentation, reproduce with decisive signals, com...
Browser automation CLI for AI-driven UI testing and review. Use when asked to "test the UI", "review the website", "check the site visually", "audit the frontend", or perform automated browser testing. Leverage...
Invoke IMMEDIATELY via brain-hooks when user requests codebase analysis, architecture review, security assessment, or quality evaluation. Do NOT explore first - the command orchestrates exploration.
Test-first bug fixing workflow. Guide users through reproducing bugs, writing failing tests, fixing code, and committing. Use when users report bugs, need to fix issues, or mention keywords like "bug", "fix", "...
Opinionated constraints for writing effective tests. Guide unit tests, integration tests, and E2E tests with quality metrics beyond coverage. Use when users write tests, review test code, or need testing strate...
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
React Native mobile development patterns for authentication, platform-specific issues, navigation, and SDK integration. Use when debugging React Native apps, fixing iOS/Android issues, handling auth flows, or i...
GDB debugging for ESP32-S3 firmware. Use when user asks to debug, gdb, breakpoint, step through, backtrace, info stack, inspect variables, or investigate crashes in ESP32 firmware.
This skill should be used when the user asks about "code cleanup", "remove unused", "dead code", "unused imports", "dependency audit", "technical debt", "refactoring", "codebase maintenance", "orphaned files",...
Analyze C++ code for real-time safety violations including heap allocations, locks, blocking calls, and unbounded operations in audio threads.
Code Reviewer persona for technical code analysis. ACTIVATE when messages contain review code, analyze code, code quality, best practices, refactor, improve code, check code, code review, look at code, feedback...
Investigation Analyst persona for systematic troubleshooting and debugging. ACTIVATE when messages contain debug, investigate, troubleshoot, analyze, diagnose, error, bug, root-cause, RCA, trace, or inspect key...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.