rakovi4/cleanup-chrome
.claude/skills/cleanup-chrome/SKILL.md
Kill orphaned chromedriver and headless Chrome processes left over from failed Selenium test runs. Use when Selenium tests mass-fail with Connection reset or TimeoutException, when the system feels sluggish during test runs, or when the user mentions /cleanup-chrome. Also use proactively before running frontend acceptance tests if previous runs were interrupted or stopped.
$ install --global
skillsauthnpx skillsauth add rakovi4/continue-example cleanup-chromeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:59 PM2.1s1 file scanned
SKILL.md
- name:
- cleanup-chrome
- description:
- Kill orphaned chromedriver and headless Chrome processes left over from failed Selenium test runs. Use when Selenium tests mass-fail with Connection reset or TimeoutException, when the system feels sluggish during test runs, or when the user mentions /cleanup-chrome. Also use proactively before running frontend acceptance tests if previous runs were interrupted or stopped.
Clean Up Orphaned Chrome Processes
Failed or interrupted Selenium test runs leave behind chromedriver and headless Chrome processes. These accumulate and exhaust system resources, causing new Selenium tests to fail with Connection reset / TimeoutException on the Chrome DevTools WebSocket.
Action
-
Count orphaned processes to assess the situation:
echo "chromedriver: $(tasklist //FI "IMAGENAME eq chromedriver.exe" 2>/dev/null | grep -c chromedriver)" && echo "chrome: $(tasklist //FI "IMAGENAME eq chrome.exe" 2>/dev/null | grep -c chrome)" -
Kill all chromedriver processes (these are always test-spawned):
taskkill //IM chromedriver.exe //F 2>&1 | tail -1 -
Kill all headless Chrome processes:
taskkill //IM chrome.exe //F 2>&1 | tail -1 -
Repeat kill commands until counts reach 0 — processes can respawn briefly as child processes exit. Usually 2-3 rounds suffice.
-
Clean locked test output if it exists:
rm -rf acceptance/build/test-results/frontendTest/binary 2>/dev/null
Output
Report how many processes were killed and confirm cleanup is complete.
Note
This kills ALL Chrome and chromedriver processes, including the user's own browser. Warn the user before proceeding if they might have a Chrome browser open with unsaved work.
Related Skills
rakovi4/test-usecase
testing
VerifiedTrustedCommunity
Run use-case module tests quickly. Use when user wants to run use-case tests or mentions /test-usecase command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-spec
development
VerifiedTrustedCommunity
Generate BDD test specifications for story in 6 categories (API, UI, Load, Infrastructure, Security, Integration). Use when user wants to create test cases or mentions /test-spec command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-review
testing
VerifiedTrustedCommunity
Review tests to replace loose validation (contains, isNotNull, isNotEmpty) with strict validation (isEqualTo on parsed fields). Use when user wants to improve test assertions or mentions /test-review command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-frontend
development
VerifiedTrustedCommunity
Run frontend tests. Use when user wants to run frontend unit tests or mentions /test-frontend command.
2SKILL.mdUpdated Apr 16, 2026