What problem does it solve? Restarting a local backend after Java, resource, or Maven changes is error-prone: developers often kill the wrong Java process, target a backend from another checkout, or hardcode ports and paths. This Skill provides a safe, validated restart workflow that only touches the backend owned by the current repository checkout. ## Core Features & Use Cases - Safe Process Targeting: Stops only a PID whose metadata and live command line match the normalized JAR path of the current checkout, never killing arbitrary java.exe processes. - Validated Restart Pipeline: Loads ROOT.env.local, validates the instance, packages mes-system with Maven, starts the JAR, and waits for the configured backend port. - Use Case: After editing Java source files in your MOM checkout, run the restart script to rebuild mes-system and bring the backend back up without risking other running Java services on your machine. ## Quick Start Ask the AI to restart the backend for the current MOM checkout using the repository-local restart script after your latest Java changes.