erne-debug

Engineering Community

Repo stars 36
License MIT
Author repo everything-react-native-expo

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: ERNE — Systematic diagnosis of bugs using the performance-profiler agent You are executing the /erne-debug command. Use the perf…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Process”, “Step 1: Reproduce”, “Step 2: Classify the Bug”, “Step 3: Investigate”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name erne-debug directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Process / Step 1: Reproduce / Step 2: Classify the Bug” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

/erne-debug — Systematic Diagnosis

You are executing the /erne-debug command. Use the performance-profiler agent for systematic bug diagnosis.

Process

Step 1: Reproduce

Define exact reproduction steps:

Starting state
Actions taken
Expected behavior
Actual behavior
Environment (device, OS, Expo SDK version)

Step 2: Classify the Bug

Category	Indicators	First Check
Crash	App terminates	Check Metro logs, Hermes stack trace
Render	Visual glitch, wrong layout	Check component tree, re-render count
State	Wrong data displayed	Check Zustand store, TanStack Query cache
Navigation	Wrong screen, broken back	Check Expo Router history, params
Performance	Jank, slow response	Check FPS, bundle size, memory
Network	Failed API calls	Check request/response, auth tokens
Native	Platform-specific issue	Check native logs (Xcode/Logcat)

Step 3: Investigate

JavaScript layer:

# Check Metro bundler logs
# Search for errors/warnings in console output
# Add strategic console.log at suspected points

React layer:

Component re-render tracking (React DevTools)
Props/state inspection
Effect dependency analysis

Native layer (if agent-device available):

Screenshot current state
Navigate through repro steps visually
Capture native crash logs

Step 4: Fix & Verify

Identify root cause
Implement minimal fix
Verify fix resolves the issue
Check for regression (run related tests)
Document what caused it and why

Output

## Bug Report

### Summary
[One-line description]

### Root Cause
[Technical explanation]

### Fix Applied
[Files changed with explanation]

### Verification
[Steps taken to verify fix]
[Test results]

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 94 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @JubaKitiashvili · MIT
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview erne-debug.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# /erne-debug — Systematic Diagnosis

You are executing the `/erne-debug` command. Use the **performance-profiler** agent for systematic bug diagnosis.

## Process

### Step 1: Reproduce
Define exact reproduction steps:
1. Starting state
2. Actions taken
3. Expected behavior
4. Actual behavior
5. Environment (device, OS, Expo SDK version)

### Step 2: Classify the Bug

| Category | Indicators | First Check |
|----------|-----------|-------------|
| **Crash** | App terminates | Check Metro logs, Hermes stack trace |
| **Render** | Visual glitch, wrong layout | Check component tree, re-render count |
| **State** | Wrong data displayed | Check Zustand store, TanStack Query cache |
| **Navigation** | Wrong screen, broken back | Check Expo Router history, params |
| **Performance** | Jank, slow response | Check FPS, bundle size, memory |
| **Network** | Failed API calls | Check request/response, auth tokens |
| **Native** | Platform-specific issue | Check native logs (Xcode/Logcat) |

### Step 3: Investigate

**JavaScript layer:**
```bash
# Check Metro bundler logs
# Search for errors/warnings in console output
# Add strategic console.log at suspected points
```

**React layer:**
- Component re-render tracking (React DevTools)
- Props/state inspection
- Effect dependency analysis

**Native layer (if agent-device available):**
- Screenshot current state
- Navigate through repro steps visually
- Capture native crash logs

### Step 4: Fix & Verify
1. Identify root cause
2. Implement minimal fix
3. Verify fix resolves the issue
4. Check for regression (run related tests)
5. Document what caused it and why

## Output
```
## Bug Report

### Summary
[One-line description]

### Root Cause
[Technical explanation]

### Fix Applied
[Files changed with explanation]

### Verification

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Process → Step 1: Reproduce → Step 2: Classify the Bug → Step 3: Investigate → Step 4: Fix & Verify → Output
terms    -> performance-profiler · Crash · Render · State · Navigation · Performance · Network · Native
files/cmd -> /erne-debug · request/response · Xcode/Logcat · errors/warnings · Props/state
body sha256 -> 32ed861dc28e