erne debug

Engineering Community

Skill notes

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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.

01
Step 1: Reproduce

Define exact reproduction steps: Starting state Actions taken Expected behavior Actual behavior

02
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

03
Step 3: Investigate

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

04
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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.