Skill UI

This specialized skill acts as an expert debugger, designed for deep root cause analysis of software errors, test failures, and unexpected behavior. It guides the user through systematic debugging processes, including capturing stack traces, isolating failure points, implementing minimal fixes, and providing comprehensive reports detailing the root cause, evidence, specific code patches, and prevention recommendations. Ideal for complex bug resolution and quality assurance.

This expert guide provides a systematic, structured methodology for debugging complex software issues. It teaches users how to analyze stack traces, correlate logs, establish consistent reproduction steps, and apply hypothesis-driven testing to isolate and resolve bugs, crashes, or unexpected behavior in any codebase. Essential for professional troubleshooting and quality assurance.

This skill is designed for advanced error detective work. It analyzes complex log streams, correlates stack traces across distributed systems, and detects anomalous error patterns. It helps identify root causes by correlating errors with system deployments and changes, providing actionable findings for immediate fixes and long-term prevention strategies.

This bundle is designed to collect comprehensive diagnostic data from the Guidewire ecosystem. It captures critical information including Cloud API responses, Gosu stack traces, server logs, OAuth token status, and batch process statuses. Use it to aid in debugging, troubleshooting, and performance analysis within Guidewire applications.

A comprehensive utility designed to gather all necessary diagnostic evidence for troubleshooting complex LangChain failures. It captures environment snapshots, dependency versions, detailed execution traces (including LLM calls and tool usage), and error stack traces. Use this bundle when preparing detailed GitHub bug reports or conducting LangSmith tracing.

A comprehensive guide to integrating Sentry into continuous integration and continuous deployment (CI/CD) pipelines (e.g., GitHub Actions, GitLab CI, CircleCI). This skill automates complex tasks such as creating releases, uploading source maps for readable stack traces, associating commits, and tracking deployment environments, ensuring rapid and accurate debugging of production errors.

This skill guides the setup of distributed tracing and performance monitoring using Sentry. It covers configuring the SDK (e.g., setting tracesSampleRate) to capture latency, identify performance bottlenecks, and trace requests across the entire application stack. It demonstrates how to create manual spans for business logic and utilizes profiling for deeper performance insights, ensuring comprehensive application observability.

This guide details how to use the Sentry CLI to manage the full application release lifecycle. Users can create versioned releases (using Semver or SHA), upload source maps to deminify stack traces, and associate specific git commits. This ensures that every error is accurately linked to the exact code version and deployment that caused it, significantly improving debugging and observability in CI/CD pipelines.

This skill enables AI-assisted debugging and comprehensive error analysis within the development environment. It utilizes Cascade to analyze complex error messages, stack traces, and surrounding code context to identify root causes. Use it when troubleshooting code or encountering runtime errors to receive detailed fix recommendations and prevention strategies.

Improves Go error handling by treating errors as structured data. This utility adds critical context—such as domain, user IDs, stack traces, and machine-readable error codes—to standard Go errors. This capability is vital for enhancing observability, enabling APM tools (like Sentry or Datadog) and on-call engineers to diagnose complex issues quickly without relying on manual log correlation.

Performs a systematic and structured investigation to determine the true source of bugs, errors, and unexpected system behavior, rather than merely treating symptoms. This method utilizes techniques like the Five Whys, hypothesis-driven testing, stack trace analysis, and gathering evidence (logs, git diffs) across multiple phases. It is ideal for complex, intermittent, or deeply rooted technical issues in software development.

Ensures every framework-specific decision is traced to authoritative docs: detect stack versions, fetch relevant pages, implement documented patterns, cite sources, and flag conflicts before committing code.