restart

Name: restart
Availability: InStock
Author: ArthTech-AI

Kill port-bound processes and restart uvicorn backend and npm frontend servers.

Updated Aug 27, 2026

Search Tags:#frontend #npm #backend #health check #restart #local development #uvicorn

Ready to run

npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill restart-arthtech-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: restart
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/tests/fixtures/claude-setups/poweruser/.claude/skills/restart
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill restart-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually stopping and relaunching local development services when your app gets stuck, crashes, or needs a clean reboot.

Core Features & Use Cases

Port Cleanup: Terminates processes holding the standard backend and frontend ports so fresh instances can start cleanly.
Service Relaunch: Brings up the backend and frontend development servers in the correct order for a full local reset.
Health Confirmation: Verifies the backend is responding after restart so you know the environment is ready.
Use Case: Ideal when a developer needs to recover a broken local Taskflow session without hunting for lingering processes or restarting each service by hand.

Quick Start

Ask the assistant to restart the local Taskflow backend and frontend services and confirm that the backend health check passes.

Frequently Asked Questions about restart

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

FAQPage Schema

How do I restart my local development stack when ports are already in use?▼

Restarting local dev servers involves killing existing processes on ports 3000 and 8000, relaunching the backend with uvicorn and frontend with npm, and verifying the backend is healthy at the /health endpoint.

What is the best way to recover a crashed local full-stack environment?▼

Recovering a crashed local full-stack environment requires terminating lingering port-bound processes, bringing the backend and frontend servers back up in the correct order, and running a health check to confirm the environment is ready.

Does this local restart process work with uvicorn and npm?▼

Yes, this local restart process works specifically with uvicorn and npm, targeting full-stack Taskflow-style environments by relaunching the backend and frontend development servers together after clearing the required ports.

Why does my local backend health check fail after manually restarting servers?▼

Your local backend health check might fail after manually restarting servers because lingering processes still hold port 8000, preventing the uvicorn backend from binding correctly and requiring a thorough port cleanup before relaunch.

When do I need to clean up ports for a local development reboot?▼

You need to clean up ports for a local development reboot when your app gets stuck, crashes, or requires a clean slate, ensuring fresh uvicorn and npm instances can start cleanly without port conflicts.