x-bug-triage

# X Bug Triage Closed-loop bug triage from public X/Twitter complaints to clustered, evidence-backed GitHub issues. ## Overview Product teams learn about bugs from X/Twitter hours before internal monitoring catches them. This skill automates the pipeline: ingest complaints, classify and cluster them by bug family, scan repos for corroborating evidence, route to owners, and file issues — all with human confirmation gates. Results display directly in the terminal with optional Slack delivery for team review. ## Prerequisites - X API bearer token configured at `~/.claude/channels/x-triage/.env` - SQLite database initialized (`bun run db:migrate`) - `config/approved-accounts.json` and `config/approved-searches.json` populated - GitHub CLI (`gh`) for issue filing Verify environment before starting: ``` !test -f data/triage.db && echo "DB ready" || echo "Run: bun run db:migrate" ``` ``` !test -f config/approved-accounts.json && echo "Accounts configured" || echo "Missing: config/approved-accounts.json" ``` ## Instructions ### Step 1: Intake 1. Resolve account username to ID: `mcp__triage__resolve_username` 2. Fetch mention timeline: `mcp__triage__fetch_mentions` 3. Run approved searches: `mcp__triage__search_recent` 4. Cross-reference mentions with search results for completeness 5. Hydrate conversation threads for posts with conversation_id: `mcp__triage__fetch_conversation` 6. Fetch quote tweets for high-engagement posts: `mcp__triage__fetch_quote_tweets` After intake...