erne debug
- Repo stars 36
- License MIT
- Author repo everything-react-native-expo
- Domain
- 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
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @JubaKitiashvili · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
Define exact reproduction steps: Starting state Actions taken Expected behavior Actual behavior
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
JavaScript layer: React layer: Component re-render tracking (React DevTools) Props/state inspection Effect dependency analysis
Identify root cause Implement minimal fix Verify fix resolves the issue Check for regression (run related tests) Document what caused it and why
# /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
[Steps taken to verify fix]
[Test results]
```
Listed in source order.
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
Step 1: Reproduce
Define exact reproduction steps: Starting state Actions taken Expected behavior Actual behavior
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
Step 3: Investigate
JavaScript layer: React layer: Component re-render tracking (React DevTools) Props/state inspection Effect dependency analysis
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