This skill should be used when the user asks about "code duplication", "jscpd", "DRY principle", "duplicate code", "clone detection", "code consolidation", or needs guidance on when and how to consolidate duplicate Go code.
Token-efficient codebase search using ripgrep with JSON output. Reduces token usage by 90-95% vs standard grep. Use for any codebase search to save tokens.
Automatically detect project tech stack, frameworks, and development context
This skill should be used when the user asks about "metaprogramming", "DSL", "domain-specific language", "method_missing", "define_method", "class_eval", "instance_eval", "module_eval", "hooks", "included", "extended", "inherited", "singleton class", "eigenclass", "dynamic methods", "eval", or needs guidance on Ruby metaprogramming techniques.
Reads MetaTrader 5 log files to validate indicator execution, unit tests, and compilation errors. Use when user mentions Experts pane, MT5 logs, errors, or asks "did it work". Triggers - check logs, did it work, Experts pane, Print output, runtime errors, debug output. (project)
Debug WebF app runtime issues with Chrome DevTools (console/network/elements) and JS-side troubleshooting. Use when the user mentions DevTools console, network tab, stack traces, blank screen, layout measurement issues, or failing network requests.
Systematically trace bugs backward through call stack to find original trigger
Comprehensive inclusion analysis of code, examining language, internationalization, assumptions, and who might be excluded. Thorough review for releases or major features.
Phrack magazine article analysis, binary exploitation, vulnerability research, exploit development, Use-After-Free (UAF), heap exploitation, ROP chain, GDB debugging, pwntools, memory corruption, CVE analysis, ProFTPd exploitation, Docker exploit lab, security research, educational hacking, buffer overflow, stack exploitation, shellcode development
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
Use when user wants to debug web pages, inspect network requests, monitor console logs, or interact with web applications using Firefox DevTools
Profile native macOS/iOS apps using Time Profiler via CLI (xctrace). Use when asked to identify performance hotspots, profile CPU usage, or diagnose slow code paths without opening Instruments.
[PHASE 4] Implements and validates fixes for verified theories. Entry: PERFORMANCE_THEORIES.md has a verified theory. Outputs: Code fix, BENCHMARK_BASELINE.md new column, theory marked fixed/fix-failed. Next: Loop to PHASE 2 if performance gaps remain, otherwise done.
Test Model Context Protocol (MCP) servers using the MCP Inspector CLI
Debug bugs and errors using intel-first approach with systematic root cause analysis. Use proactively when errors occur, tests fail, or unexpected behavior appears. MUST trace from symptom to root cause with CoD^Σ reasoning.
Analyze the impact of code changes by mapping call graphs and identifying all direct and indirect dependencies. Use when users ask about blast radius analysis, code change impact, who calls a function, downstream dependencies, or risk assessment before refactoring. Traces call chains, identifies high-risk modules, and provides ranked impact analysis.
Systematic debugging workflow for CircleTel - analyzes errors, identifies root causes, proposes fixes, and validates solutions with tests
Systematic root cause analysis for debugging errors. Use when an error appears, something breaks unexpectedly, or you need to trace a problem back to its source. Prevents panic-driven debugging.
Find and fix performance issues in Leavn - main thread blocking, heavy View body computation, missing lazy loading, inefficient list rendering
Toolkit para interagir e testar aplicações web locais usando Chrome DevTools MCP. Suporta verificação de funcionalidade frontend, debugging de UI, captura de screenshots, análise de performance, inspeção de network e visualização de logs do console.
