skills.rest
paulyokota
paulyokotaCOMMUNITY
Explore all skills by this author →
GitHub

bug-discovery

Analyze Intercom symptom keywords and PostHog events to produce lean bug cards.

Updated Aug 23, 2026
Search Tags:#triage#posthog#intercom#evidence-cards#bug-discovery#signal-hunting#codepath-trace
One-click install
npx skills add https://github.com/paulyokota/FeedForward --skill bug-discovery-paulyokota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-discovery
Source: https://github.com/paulyokota/FeedForward/tree/main/.claude/skills/bug-discovery
Command: npx skills add https://github.com/paulyokota/FeedForward --skill bug-discovery-paulyokota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug discovery in product development is manual, slow, and error-prone. This skill accelerates detection of untracked bugs by scanning Intercom symptom keywords, cross-referencing reporters with PostHog failure events, and tracing codebase failure paths to generate concise bug cards.

Core Features & Use Cases

  • Intercom symptom keyword search across historical conversations to surface potential bugs.
  • Cross-reference reporters against PostHog failure events to validate signal quality.
  • Trace failure paths in the codebase to identify root causes and produce actionable Backlog cards.

Quick Start

Kick off the bug discovery workflow by initiating a symptom keyword search in Intercom and review the lean bug card results.

Frequently Asked Questions about bug-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find untracked product bugs using Intercom and PostHog?▼

Find untracked bugs by scanning Intercom symptom keywords, cross-referencing reporters with PostHog failure events, and tracing codebase failure paths to generate actionable bug cards.

What is the best way to cross-reference Intercom support tickets with PostHog analytics events?▼

The best way to cross-reference Intercom tickets with PostHog events is to match the reporters of symptom keywords against PostHog failure events to validate signal quality and uncover untracked issues.

How do I trace codebase failure paths to identify root causes for customer-reported symptoms?▼

Trace codebase failure paths by analyzing validated symptom signals from PostHog and Intercom, isolating the exact code execution route that failed, and packaging the root cause into a lean bug card.

Can I automate bug discovery across Intercom conversations and analytics data?▼

Yes, you can automate bug discovery by initiating a symptom keyword search across historical Intercom conversations to surface potential bugs, then validating them against PostHog failure events.

Does bug discovery work without pre-existing bug tracking entries in my backlog?▼

Yes, bug discovery specifically identifies untracked product bugs by hunting for raw signals across Intercom and PostHog, then packaging the findings into new publishable backlog cards.

Why are customer-reported symptoms not matching my existing PostHog failure events?▼

Customer-reported symptoms may not match PostHog failure events because the bugs are untracked; cross-referencing symptom keywords against analytics events helps validate signal quality and surface hidden issues.

Related Skills

Explore More Product & Management Skills→
EigenwiseEigenwise
15

map-codebase

Create structured codebase maps from repository files and manifests.

Community
Advanced
HechaoYannetHechaoYannet

bug-triage

Triage open bug backlogs into prioritized, sprint-ready action lists.

Community
Advanced
hmzainjamilhmzainjamil
1

Intercom Automation

Automate Intercom messaging, support routing, and user engagement workflows.

Community
Advanced
giadaf-booshagiadaf-boosha
10

ticket-triage

Categorize customer support tickets, assign priorities, and recommend routing.

Community
Advanced