cleanup-chrome

Name: cleanup-chrome
Availability: InStock
Author: rakovi4

Terminate orphaned Chrome and chromedriver processes from failed Selenium test runs.

45|13|Updated Apr 13, 2026

Search Tags:#test automation #cleanup #resource management #Selenium #orphaned processes

Ready to run

npx skills add https://github.com/rakovi4/continue-framework --skill cleanup-chrome-rakovi4

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-chrome
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/cleanup-chrome
Command: npx skills add https://github.com/rakovi4/continue-framework --skill cleanup-chrome-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the issue of orphaned Chrome and chromedriver processes left behind by failed Selenium test runs, which can lead to system resource exhaustion and test failures.

Core Features & Use Cases

Process Identification: Counts and identifies orphaned Chrome and chromedriver processes.
Process Termination: Kills all identified orphaned processes to free up system resources.
Output Reporting: Provides a report on the number of processes terminated.
Use Case: When Selenium tests mass-fail with Connection reset or TimeoutException, or when the system feels sluggish during test runs.

Quick Start

To clean up orphaned Chrome processes, run the 'cleanup-chrome' command.

Frequently Asked Questions about cleanup-chrome

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

FAQPage Schema

How do I clean up orphaned Chrome processes after failed Selenium test runs?▼

You can clean up orphaned Chrome processes by running the 'cleanup-chrome' command, which identifies leftover Chrome and chromedriver instances from failed Selenium runs and terminates them to free up system resources.

Why does my system feel sluggish during Selenium test automation?▼

Your system feels sluggish during Selenium test automation because failed runs leave behind orphaned Chrome and chromedriver processes that exhaust system resources and degrade performance.

What is the best way to kill leftover chromedriver processes causing Connection reset errors?▼

The best way to kill leftover chromedriver processes causing Connection reset errors is to run the 'cleanup-chrome' command, which systematically terminates orphaned processes and reports the total number stopped.

Do I need any dependencies to remove orphaned Chrome and chromedriver processes?▼

No, you do not need any dependencies to remove orphaned Chrome and chromedriver processes, as this Skill operates independently and executes system commands directly to terminate leftover instances.

When should I run a cleanup for orphaned Chrome processes?▼

You should run a cleanup for orphaned Chrome processes when your Selenium tests mass-fail with TimeoutException or Connection reset errors, or when you notice system sluggishness during automated test runs.