log-analyzer
Analyze application logs to detect errors, patterns, anomalies, and generate insights. Use when troubleshooting issues or analyzing system behavior.
Discover lifestyle debugging skills, compare source repositories and read the instructions for each workflow.
Analyze application logs to detect errors, patterns, anomalies, and generate insights. Use when troubleshooting issues or analyzing system behavior.
Generate, optimize, and explain SQL queries with best practices. Use when writing database queries or optimizing SQL performance.
Analyze and prioritize technical debt with refactoring recommendations. Use when evaluating code quality or planning debt reduction.
Automated code review with security, performance, and best practices analysis. Use when reviewing pull requests or analyzing code for vulnerabilities, performance issues, or maintainability concerns.
Detect code smells including long methods, large classes, duplicated code, and deep nesting. Use when identifying code quality issues or planning refactoring.
Perform security audits detecting OWASP Top 10 vulnerabilities, insecure dependencies, and security misconfigurations. Use when auditing applications for security vulnerabilities.
Browser debugging and telemetry via Chrome DevTools Protocol. Use when testing the Astro dev server, inspecting network requests, debugging console errors, capturing screenshots, or interacting with DOM element...
This skill should be used when the user mentions "test javascript", "bun test", "unit test", "happy-dom", "test client-side js", "dom mocking", "browser tests", "test theme toggle", "test scroll handlers", or a...
Conduct a focused performance analysis based on the Well-Architected Framework Performance Efficiency pillar. Use when user says "performance review", "wa performance", or "check performance". Analyzes scalabil...
Code review best practices for Python projects. Use when reviewing code, PRs, or diffs. Triggers on "review", "code review", "PR", "pull request", "diff", "check this", "look at this code", "quality", "refactor...
Pattern discovery and code reuse for Python projects. Use when writing new code, implementing features, or refactoring. Triggers on "pattern", "reuse", "duplicate", "extract", "helper", "refactor", "architectur...
Performance optimization guide for React and Next.js. Use when writing, reviewing, or refactoring React code, optimizing performance, or asking about React best practices.
Portfolio analytics, metrics calculation, performance tracking, and dashboard data. Use when working with analytics code, files, or integration. Invoke when navigating analytics codebase, searching for analytic...
Use OpenAI Codex CLI to answer questions about code, analyze files, or perform read-only codebase exploration. Invoke this skill when the user asks to use Codex, wants a second opinion from another AI agent, or...
Use Google Gemini CLI to answer questions about code, analyze files, or perform codebase exploration. Invoke this skill when the user asks to use Gemini, wants a second opinion from another AI, or wants to comp...
Maximum search effort mode. Launch multiple parallel agents for exhaustive codebase and documentation search. Use when you need comprehensive search results.
Deep analysis mode. Gather comprehensive context before diving deep. Use for investigation, debugging, and understanding complex systems.
Monitor applications, investigate performance issues, and analyze observability data in New Relic. Use when the user needs APM metrics, error tracking, infrastructure monitoring, or incident analysis.
4-phase debugging framework preventing "guess-and-check" fixing. Load when debugging fails or for complex bug investigation.
How to use the FlowStorm debugger to analyze Clojure/ClojureScript program executions. This skill teaches timeline exploration, value inspection, and debugging patterns using FlowStorm's recording API for runti...
Conduct comprehensive research across the codebase to answer questions, explore solutions, or understand existing implementations. Use when researching a problem, designing a new feature that interfaces with ex...
Clojure programming with naming guidelines and performance best practices. Use when writing or reviewing Clojure/ClojureScript code.
Systematically trace bugs and issues to their root cause using debugging techniques and analysis methods
코드 종합 분석 (품질/보안/성능/아키텍처). Use when: (1) 코드 분석 요청, (2) 보안 취약점 스캔, (3) 성능 병목 식별, (4) 아키텍처 검토.
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.