Omnibus Instrument Error Tracking

PostHogOfficialCreated by PostHog

Skill
Tool integration
Data and AI
MIT
Low risk

From the author

Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.

— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured procedure for integrating PostHog error tracking into various software projects. It guides the user through detecting their platform, installing the necessary SDK, enabling automatic exception capture, and implementing manual error reporting in critical code paths. The skill also covers essential configuration steps like setting up environment variables and uploading source maps to ensure stack traces remain readable and actionable.

What it does

Detects the project's platform and language to determine the correct PostHog SDK installation path.
Automates the installation and initialization of the PostHog SDK.
Enables exception autocapture to monitor unhandled errors automatically.
Assists in adding manual capture points for specific error boundaries and catch blocks.
Configures source map uploads to resolve minified stack traces into readable source code.
Ensures secure management of API keys using environment variables.

When to use it

After implementing new features to ensure robust error monitoring.
During code reviews when identifying areas that lack proper exception handling.
When setting up a new project and requiring initial observability infrastructure.
When existing error tracking is insufficient or requires migration to PostHog.

Advantages

Provides a consistent, step-by-step approach across diverse technology stacks.
Reduces manual effort by automating SDK setup and configuration.
Improves debugging efficiency by ensuring stack traces are mapped to source code.
Promotes security best practices by enforcing the use of environment variables.

Usage examples

“Set up PostHog error tracking for my React project.”: The agent will analyze the project structure, install the PostHog SDK, configure exception autocapture, and guide you through setting up source map uploads.
“I need to add manual error reporting to my Python catch blocks.”: The agent will identify your existing error handling logic and insert the appropriate PostHog captureException calls.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/omnibus-instrument-error-tracking/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip omnibus-instrument-error-tracking.zip -d .agents/skills

Documentation by PostHog

Add PostHog error tracking

Use this skill to add PostHog error tracking that captures and monitors exceptions in your application. Use it after implementing features or reviewing PRs to ensure errors are tracked with full stack traces and source maps. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any platform or language.

Supported platforms: React, Next.js, Web (JavaScript), Node.js, Python, Ruby, Ruby on Rails, Go, Angular, Svelte, Nuxt, React Native, Flutter, Android, and Hono.

Instructions

Follow these steps IN ORDER:

STEP 1: Analyze the codebase and detect the platform.

Look for dependency files (package.json, requirements.txt, go.mod, Gemfile, composer.json, etc.) to determine the language and framework.
Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb) to determine the package manager.
Check for existing PostHog setup (SDK initialization, env vars, etc.). If PostHog is already installed and initialized, skip to STEP 4.

STEP 2: Research instrumentation. (Skip if PostHog is already set up.) 2.1. Find the reference file below that matches the detected platform — it is the source of truth for SDK initialization, exception autocapture, and framework-specific error tracking patterns. Read it now. 2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com/docs as the primary search source.

STEP 3: Install and initialize the PostHog SDK. (Skip if PostHog is already set up.)

Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.
Always install packages as a background task. Don't await completion; proceed with other work immediately after starting the installation.
Follow the framework reference for where and how to initialize.

STEP 4: Enable exception autocapture.

Follow the platform reference to enable exception autocapture. This automatically captures unhandled exceptions without additional code.

STEP 5: Add manual error captures.

Identify error boundaries, catch blocks, and critical user flows where errors should be explicitly captured.
Add posthog.captureException() or the platform-equivalent at these locations.
Do not alter the fundamental architecture of existing error handling. Make additions minimal and targeted.
You must read a file immediately before attempting to write it.

STEP 6: Upload source maps (frontend/mobile only).

Configure source map uploads so stack traces resolve to original source code, not minified bundles.
Follow the platform-specific reference for upload configuration (build plugins, CI scripts, etc.).

STEP 7: Set up environment variables.

If an env-file-tools MCP server is connected, use check_env_keys to see which keys already exist, then use set_env_values to create or update the PostHog API key and host.
Reference these environment variables in code instead of hardcoding them.

STEP 8: Verify and clean up.

Check the project for errors. Look for type checking or build scripts in package.json.
Ensure any components created were actually used.
Run any linter or prettier-like scripts found in the package.json.

Reference files

references/react.md - React error tracking installation - docs
references/web.md - Web error tracking installation - docs
references/nextjs.md - Next.js error tracking installation - docs
references/node.md - Node.js error tracking installation - docs
references/python.md - Python error tracking installation - docs
references/ruby.md - Ruby error tracking installation - docs
references/ruby-on-rails.md - Ruby on rails error tracking installation - docs
references/go.md - Go error tracking installation - docs
references/angular.md - Angular error tracking installation - docs
references/svelte.md - Sveltekit error tracking installation - docs
references/nuxt.md - Nuxt error tracking installation (v3.7 and above) - docs
references/react-native.md - React native error tracking installation - docs
references/flutter.md - Flutter error tracking installation - docs
references/android.md - Android error tracking installation - docs
references/hono.md - Hono 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

Each platform reference contains SDK-specific installation and manual capture patterns. Find the one matching the user's stack.

Key principles

Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing code.
Autocapture first: Enable exception autocapture 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.

Files

ATTRIBUTION.mdAdded by AutoGineer969 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md5.6 KiB
references/alerts.md4.1 KiB
references/android.md3.9 KiB
references/angular.md8.2 KiB
references/assigning-issues.md5.5 KiB
references/fingerprints.md3.4 KiB
references/flutter.md9.1 KiB
references/go.md4.8 KiB
references/hono.md2.9 KiB
references/monitoring.md8.6 KiB
references/nextjs.md13.2 KiB
references/node.md3.7 KiB
references/nuxt.md4.5 KiB
references/python.md5.1 KiB
references/react-native.md6.2 KiB
references/react.md5.4 KiB
references/ruby-on-rails.md3.5 KiB
references/ruby.md2.5 KiB
references/svelte.md4.8 KiB
references/upload-source-maps.md2.7 KiB
references/web.md5.4 KiB

references/assigning-issues.md

Assign issues to teammates - Docs

Error tracking enables you to assign issues to specific PostHog roles or teammates. This helps your team find relevant issues through filtering. You can also set up team-specific alerting to notify them when assigned issues are created or reopened.

Assign issues

You can manually assign issues as you triage them in the UI. This can be done both in the issue list and issue detail pages.

Image: Error tracking assignment UIImage: Error tracking assignment UI

In your error tracking issue list, click the unassigned selector under each issue to assign it to a role or user.
On the detail page of each issue, click the Assignee selector to assign it to a role or user.

Want to assign issues to a team rather than an individual teammate? You can create a role in your project settings.

Image: Error tracking role assigneesImage: Error tracking role assignees

Automatic issue assignment

You can set up automatic issue assignment through a set of rules. This can be configured in the error tracking settings using auto assignment rules.

Image: Error tracking auto assignment rulesImage: Error tracking auto assignment rules

Assignment conditions are evaluated against the properties of the exception event that created the issue. Because assignment rules are evaluated during ingestion, the stack trace (if present) will be unminified, which enables filtering on exception properties such as function name and source file.

Issues can be automatically assigned to a role or user by configuring a set of filters. These filters can be configured to match any or all of the criteria.

You can configure automatic assignment to filter on any event property in PostHog. When there are multiple values for a property, the filters return true if it matches any of the values. For example, if you have multiple exception_functions values, the filters returns true if it matches any of the functions.

Here are some common properties you can filter on:

Property	Event property	Description
Exception type	$exception_types	The type of exception(s) that occurred
Exception message	$exception_values	The message(s) detected on the error
Exception function	$exception_functions	The function(s) where the exception occurred
Exception source	$exception_sources	The source file(s) where the exception occurred
Exception was handled	$exception_handled	Whether the exception was handled by the application
Device type	$device_type	The type of device that the error occurred on
Browser	$browser	The browser that the error occurred in
Current URL	$current_url	The URL that the error occurred on
Feature flag	$feature_flag	The feature flag that the error occurred on

You can also set custom properties on the error tracking event to filter on. For example, setting a custom params_received property to provide more context or debug information.

Order of issue assignment rules

Issue assignment filters are evaluated in the order they are configured. They can also be reordered once created. The first filter that matches is used to assign the issue. This means you should configure the most specific filters first, and then the more general filters later.

Disabled assignment rules

Assignment rules can become disabled if an error occurs during ingestion. When a rule is disabled, a banner displays the original error message. To re-enable the rule, edit it to fix the problem and save your changes. If the issue persists, reach out to support.

Alerting based on assignment

A common use case for automatic issue assignment is to alert assignees of new issues. Once the issues are automatically assigned, you can set up alerts to notify the assignee. See the alerts guide for more information.

Create external issues

You can also create issues in external tracking systems like GitHub Issues, Linear, GitLab, or Jira.

First, set up an integration with your tracking system. Then, from an issue's details page, under External references, click Create issue.

Image: Error tracking create issue in external tracking systemImage: Error tracking create issue in external tracking system

The new issue will have a partial stack trace and a link to the issue in PostHog.

If you use another issue tracking system and would like to request it, let us know in-app.

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server, Needs an API key, Needs Python, Needs Node.js

Security

What our scanner noticed· Low risk

Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

PostHog

Publisher

PostHog (Official)

Source

PostHog/skills · skills/posthog/error-tracking/skills/all · commit a5d30e7

Licence

MIT License (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

Also distributed in

PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog or PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omnibus-instrument-error-tracking.zip