Observability Fixer FAQs

Question 1

How does it handle version control?

Accepted Answer

The skill automatically creates a dedicated infrastructure branch (infra/observability-...) before applying any changes to ensure a clean audit trail and safe code reviews.

Question 2

Does it fix everything at once?

Accepted Answer

No, it focuses on the single highest-priority issue per invocation. This ensures each fix is independently verified and easier to troubleshoot.

Question 3

Which specific tools does this skill support?

Accepted Answer

It is optimized for industry-standard tools including Sentry for error tracking, PostHog for analytics, and Pino for structured logging, specifically for Next.js and TypeScript environments.

Question 4

How does the skill prioritize which observability issue to fix?

Accepted Answer

The skill follows a strict priority hierarchy, starting with P0 issues (error tracking and health endpoints), then moving to P1 (logging and alerting), P2 (analytics), and P3 (performance monitoring).

Question 5

Can I see the issues without applying any fixes?

Accepted Answer

Yes, you can use the /log-observability-issues command to generate a report of all identified gaps without making any changes to your code.

Observability Fixer

Key Features

Use Cases

Observability Fixer

Key Features

Use Cases