dev-server

Name: dev-server
Availability: InStock
Author: Civitai

Manage Next.js dev servers across git worktrees with start, stop, and log access.

7.2k|732|Updated Oct 11, 2022

Search Tags:#logging #Next.js #worktree #session-management #dev-server #daemon #port-control

Ready to run

npx skills add https://github.com/civitai/civitai --skill dev-server-civitai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-server
Source: https://github.com/civitai/civitai/tree/main/.claude/skills/dev-server
Command: npx skills add https://github.com/civitai/civitai --skill dev-server-civitai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Centralizes the management of Next.js dev servers across multiple git worktrees, reducing context switching and manual coordination among developers.

Core Features & Use Cases

Centralized control to start, stop, and read logs for any worktree.
Per-session port management with environment variable injection to ensure isolated, predictable runtimes.
Log aggregation and readiness detection (log-based or health-check) across all sessions for quick debugging.
Session-based log access to support collaboration and faster issue resolution.

Quick Start

Start a dev server for the current worktree and tail its logs.

Frequently Asked Questions about dev-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage multiple Next.js dev servers across different git worktrees?▼

You can manage multiple Next.js dev servers across git worktrees using a centralized daemon that coordinates per-session ports, environment variable injection, and log aggregation to isolate and control each running instance.

How does port control work for Next.js dev servers in a multi-worktree environment?▼

Port control for Next.js dev servers in a multi-worktree environment works by assigning per-session ports with environment variable injection, ensuring each worktree runs an isolated, predictable runtime without manual port configuration.

Can I aggregate and access logs for specific Next.js dev server sessions?▼

Yes, you can aggregate and access logs for specific Next.js dev server sessions through centralized REST endpoints that fetch session-based logs, supporting quick debugging and faster issue resolution across worktrees.

What is the best way to start and stop Next.js dev servers across worktrees?▼

The best way to start and stop Next.js dev servers across worktrees is through centralized REST endpoints that manage session lifecycles, handle readiness detection via health checks, and streamline collaboration.

Do I need to manually configure environment variables for each Next.js worktree session?▼

No, you do not need to manually configure environment variables for each Next.js worktree session because the daemon automatically handles environment injection per session to ensure isolated runtimes.

Why does my Next.js dev server readiness check fail when starting multiple worktree sessions?▼

Next.js dev server readiness checks might fail if health-check or log-based detection encounters port conflicts, but the daemon prevents this by enforcing per-session port control and monitoring readiness across all sessions.