investigate-pylon
Investigate Pylon Ticket
Investigate Pylon issue $ARGUMENTS.
Step 1: Gather context
- Fetch the Pylon issue using
get_issuewith the issue number - Fetch the full message history using
get_issue_messages - Fetch the customer account using
get_account - Fetch the customer contact using
get_contact
The message thread is often more important than the issue body. Pay close attention to:
- Follow-up messages where the customer added crucial details
- Prior replies from colleagues (don't contradict them)
- What the customer is currently waiting on, which may differ from the original question
- Whether the issue has already resolved itself
Use the customer's first name in any draft replies. Note their account tier (Starter, Starter Plus, etc.) to calibrate expectations around feature availability.
More from lightdash/lightdash
developing-in-lightdash
Use when working with Lightdash YAML files, dbt models with Lightdash metadata, the lightdash CLI (deploy, upload, download, preview, lint, sql, set-warehouse), or creating/editing charts, dashboards, metrics, and dimensions as code
91frontend-style-guide
Apply the Lightdash frontend style guide when working on React components, migrating Mantine v6 to v8, or styling frontend code. Use when editing TSX files, fixing styling issues, or when user mentions Mantine, styling, or CSS modules.
64ld-permissions
Guide for Lightdash's CASL-based authorization system. Use when working with scopes, custom roles, abilities, permissions, ForbiddenError, authorization, or access control. Helps with adding new scopes, debugging permission issues, understanding the permission flow, and creating custom roles.
48debug-local
Debug the Lightdash app using PM2 logs, Spotlight traces, and browser automation. Use when investigating issues, tracking down bugs, understanding request flow, or correlating frontend actions with backend behavior.
23har-replay
Replay a HAR file as a mock backend to reproduce frontend performance issues with production data. Use when asked to replay a HAR file, reproduce a dashboard with a HAR, or test frontend performance with captured traffic.
23graphite
|
3