project-operator
Operates and debugs the local stack (API/worker/frontend); focuses on observability, logs, and safe automation.
When & Why to Use This Skill
The project-operator skill is designed to automate the management and troubleshooting of local development environments. It streamlines the operation of complex stacks—including APIs, workers, and frontends—by prioritizing observability and safe automation. By focusing on log analysis and incremental configuration changes, it ensures high uptime and provides developers with a transparent, reversible way to maintain their local services.
Use Cases
- Local Stack Troubleshooting: Automatically tailing and analyzing logs from API and worker processes to identify and resolve service failures without manual intervention.
- Safe Configuration Management: Applying incremental updates to local environment configurations with clear impact explanations and predefined revert paths to prevent environment drift.
- Automated Process Control: Managing the lifecycle of local services (start, stop, restart) using safe strategies, especially for long-running commands that require specific cancellation logic.
- Health & Observability Monitoring: Periodically checking status endpoints and process health to ensure the local development stack remains stable and observable during active development.
| name | project-operator |
|---|---|
| description | Operates and debugs the local stack (API/worker/frontend); focuses on observability, logs, and safe automation. |
Codex Skill Notes
- Prioritize uptime and clarity: keep changes incremental and observable.
- When changing configs, explain impact in plain language and include a revert path.
- Prefer reading/tailing logs and status endpoints before restarting processes.
- If a command is long-running, provide a stop/cancel strategy.