Can it help with frontend loading issues?

Yes, it includes specific routines for clearing the frontend zombie processes and restarting the npm development server.

How does it fix port conflicts?

It uses lsof to identify the process IDs (PIDs) listening on the specific TCP ports and provides the exact kill commands to clear those zombie processes.

Why does it delete __pycache__ folders?

Stale bytecode often causes runtime errors when Python dataclasses change but the compiled files don't update; deleting them forces a clean re-compile.

When should I use the oe-backend-startup-triage skill?

Use this skill whenever your local backend fails to start, ports 8000 or 3000 are blocked, or you see 'unexpected keyword argument' errors on your first request.

OpenEvent Backend Startup Triage

Name: OpenEvent Backend Startup Triage
Author: shami-ah

byshami-ah

Desarrollo de API

Troubleshoots and resolves backend startup failures, port conflicts, and stale bytecode issues for OpenEvent-AI environments.

Acerca de

The oe-backend-startup-triage skill is designed to streamline the debugging process for local development environments when the backend fails to initialize. It provides specific patterns for identifying and killing zombie processes on ports 8000 and 3000, clearing stale Python bytecode caches that often cause 'unexpected keyword argument' errors, and verifying import integrity after refactors. This skill ensures a stable development workflow by automating the cleanup of common environment-related friction points.

Características Principales

Environment variable configuration for bytecode-free execution
Standardized startup paths via canonical development scripts
Comprehensive cleanup of stale .pyc and __pycache__ directories
Import sanity checks and refactor verification triggers
0 GitHub stars
Automated identification and termination of blocked port listeners

Casos de Uso

Resolving 'address already in use' errors when restarting Uvicorn or Node.js servers
Debugging missing exports or ImportErrors after significant code refactoring
Fixing internal server errors on first requests caused by outdated dataclass caches

Acerca de

Características Principales

Environment variable configuration for bytecode-free execution
Standardized startup paths via canonical development scripts
Comprehensive cleanup of stale .pyc and __pycache__ directories
Import sanity checks and refactor verification triggers
0 GitHub stars
Automated identification and termination of blocked port listeners

Casos de Uso

Resolving 'address already in use' errors when restarting Uvicorn or Node.js servers
Debugging missing exports or ImportErrors after significant code refactoring
Fixing internal server errors on first requests caused by outdated dataclass caches