Codebase exploration and location finder for the Raamattu Nyt monorepo. Use when finding where specific functionality is implemented, locating constants/tokens/config values, discovering file patterns, or answering "where is X coded?" questions. Helps other skills and agents locate code quickly.
Review code for best practices and potential issues. Use when reviewing code, checking PRs, or analyzing code quality.
Analyze OSS solutions for code quality, documentation, and best practices using Context7, DeepWiki, and Perplexity. Use when users request repository analysis, code review, library documentation lookup, or need insights about GitHub projects and open-source technologies.
Use this agent when understanding the historical context and evolution of code changes, tracing the origins of specific code patterns, identifying key contributors and their expertise areas, or analyzing patterns in commit history. Triggers on requests like "git history analysis", "why was this written", "who owns this code".
This skill should be used when performing exhaustive code reviews using multi-agent analysis, ultra-thinking, and Git worktrees for deep local inspection. It applies to PR reviews, branch comparisons, and comprehensive code quality assessments.
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 guidance on trace file formats, event types, common failure patterns, or troubleshooting ctx-monitor output.
Precisely filter and query Langfuse traces/observations using advanced filter operators for debugging and optimization workflows
OpenTelemetry observability - use for distributed tracing, metrics, instrumentation, Sentry integration, and monitoring
Implement error tracking, performance monitoring, and user issue detection. Use when adding error handling, Web Vitals reporting, or debugging production issues.
Search and analyze DealerVision production logs via SolarWinds Observability API. Use when investigating errors, debugging issues, checking system health, or when the user mentions logs, SolarWinds, production errors, or system monitoring. Requires the `logs` CLI tool to be installed.
Tracing (OTEL), Metrics (Prometheus), and Structured Logging
Evaluate logging coverage, error tracking, debugging capabilities, and monitoring patterns. Use when investigating production issues becomes difficult, after incidents, or when expanding monitoring coverage.
Debug and analyze {{PROJECT_NAME}} errors and exceptions. Use when investigating crashes, error patterns, performance issues, or understanding what went wrong in production. Covers error queries by agent, exception types, and common debugging scenarios.
Routes analysis and debugging tasks. Triggers on analyze, debug, troubleshoot, review, audit, security, performance, optimize, investigate, trace.
Tag logs, metrics, and distributed traces with REQ-* keys for production traceability. Enables backward traceability from runtime issues to requirements to intent. Use when deploying code or setting up observability.
Query and analyze logs using Loki and LogQL. Provides patterns for correlation ID tracing, error investigation, and service debugging using HuleEdu's structured logging. Integrates with Context7 for latest Loki documentation.
Implement error tracking, performance monitoring, and user issue detection. Use when adding error handling, Web Vitals reporting, or debugging production issues.
Manage full-stack observability using Logfire (logging/tracing) and OpenObserve (storage/visualization).
Native crash reporting, hang diagnostics, and performance metrics using Apple's MetricKit framework without third-party dependencies. Use this skill when implementing MXMetricManagerSubscriber, creating custom signpost categories, integrating OSLog with MetricKit, or processing diagnostic and metric payloads.
Jaeger/OpenTelemetry patterns plus Skriptoteket tracing conventions (async context propagation, correlation, debugging).
Observability with Prometheus, Grafana, logging, and tracing
Integrate Playwright tests with OpenTelemetry, Grafana, Prometheus, Loki, and Tempo. Use when debugging test failures across distributed systems, measuring test performance, creating test dashboards, or correlating tests with backend traces.
