lightdash/lightdash✦ 精选0°

debug-local

仓库创建 2021年3月19日最近提交 3 小时前SkillHot 收录 3 小时前
▸ 精选理由

系统化排查流程,强调证据优先并避免盲目改动。

这个 Skill 做什么

指导使用 PM2、Spotlight 与浏览器自动化收集证据并定位本地问题。

用 PM2 日志、Spotlight traces 和浏览器自动化把本地问题的证据收集齐,定位请求从前端到后端的链路。遇到本地重现不了的 bug、要追踪错误或把前端操作和后端行为对应起来时用。特点是同时关联 PM2 logs、traces 和自动化 replay,先收集能证明根因的证据再修复,避免盲目改代码。

▸ 展开 SKILL.md 英文原文

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.

开发编程本地调试日志分析追踪重现问题Claude Code
6.0k
Stars
750
Forks
21
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/lightdash/lightdash/main/.claude/skills/debug-local/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/lightdash/lightdash/main/.claude/skills/debug-local/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Debugging Lightdash

## Iron Law

**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.**

Do not edit application code until you have a confirmed root cause hypothesis backed by evidence (logs, traces, reproduction). Fixing symptoms creates whack-a-mole debugging.

---

## Phase 1: Gather Evidence

Before forming any hypothesis, collect facts.

### 1. Collect symptoms

Read error messages, stack traces, and reproduction steps. If the user hasn't provided enough context, ask ONE clarifying question.

### 2. Check recent changes

```bash
git log --oneline -20 -- <affected-files>
```

Was this working before? A regression means the root cause is in the diff.

### 3. Check logs and traces

```ba
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有