mcpField
E
error-tracking-go

error-tracking-go

github.com/posthogDevelopment7692 installsUpdated today
Repository

About error-tracking-go

A skill for adding PostHog error tracking to Go applications. It provides implementation guidance that preserves existing error handling and covers autocapture, manual capture, and source maps.

Key features

  1. 01Install PostHog error tracking in Go
  2. 02Use environment variables for configuration
  3. 03Enable exception autocapture first
  4. 04Capture exceptions at error boundaries
  5. 05Upload source maps

Use cases

  1. 01Add error tracking to a Go application
  2. 02Capture exceptions not handled globally
  3. 03Resolve stack traces to original source

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/skills --skill error-tracking-go

After installing, type/error-tracking-goin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
alerts.md
assigning-issues.md
fingerprints.md
go.md
monitoring.md
upload-source-maps.md

Details

From the project README

PostHog error tracking for Go

This skill helps you add PostHog error tracking to Go applications.

Reference files

  • references/go.md - Go error tracking installation - docs
  • references/fingerprints.md - Fingerprints - docs
  • references/alerts.md - Send error tracking alerts - docs
  • references/monitoring.md - Monitor and search issues - docs
  • references/assigning-issues.md - Assign issues to teammates - docs
  • references/upload-source-maps.md - Upload source maps - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
  • Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
  • Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.
  • Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
  • Manual capture for boundaries: Use captureException() at error boundaries and catch blocks for errors that don't propagate to the global handler.

Framework guidelines

No specific framework guidelines.

Comments

Markdown supported