mcpField
E
error-tracking-flutter

error-tracking-flutter

github.com/posthogDevelopment7693 installsUpdated today
Repository

About error-tracking-flutter

A coding skill for adding PostHog error tracking to Flutter apps. It emphasizes minimal changes, exception autocapture, and source maps.

Key features

  1. 01Flutter error-tracking guidance
  2. 02Exception autocapture setup
  3. 03Manual exception capture
  4. 04Source map upload guidance
  5. 05Environment-based configuration

Use cases

  1. 01Adding error tracking to a Flutter app
  2. 02Capturing errors at catch blocks
  3. 03Resolving stack traces to source code

Install

Copy the command and run it in a terminal.

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

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

Bundled files

References and scripts installed along with SKILL.md.

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

Details

From the project README

PostHog error tracking for Flutter

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

Reference files

  • references/flutter.md - Flutter 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