system-performance-remediation

To find and kill zombie processes, use the ps command to enumerate processes sorted by CPU usage, identify zombie PIDs, and terminate them safely. This skill audits system load and proposes targeted process termination actions for your confirmation.

System sluggishness from long coding sessions is often caused by zombie processes and long-running commands accumulating after multiple agents run. This skill diagnoses the system load and identifies specific resource-wasting processes to remediate the hang.

To safely terminate stuck processes without killing active agents, apply a rules-driven workflow that categorizes process risks, estimates impact, and shows explicit PID-level details for your confirmation before any termination occurs.

A safe kill sequence involves auditing memory and swap, listing top CPU-consuming processes with ps, categorizing risks to protect active coding agents, and proposing targeted terminations that require your explicit confirmation before execution.

You can diagnose system load and memory usage before terminating processes by running uptime, nproc, and free commands. This skill uses that system audit data to inform its recommended remediation action plan.

Yes, safe process cleanup is designed for scenarios where developers experience slow performance after long coding sessions with multiple agents. It enumerates and categorizes stuck processes while explicitly protecting your active coding agents.