test-tracker_skill

Overview

This skill manages and tests the vibereps exercise tracker UI. It provides commands to launch the tracker in quick or normal modes, restart it by killing existing instances, and run targeted tests or demos. Use it to reliably start a fresh tracker process and control which exercises are shown.

How this skill works

The skill issues process control commands to terminate any running exercise_tracker.py instance and then starts a new instance with the requested mode or environment variables. It can limit visible exercises via VIBEREPS_EXERCISES, temporarily disable the tracker with VIBEREPS_DISABLED, and clear temporary Chrome state to fix display issues. It also includes a basic port check to detect a running instance.

When to use it

• You need to launch the exercise tracker for a short demo while another process runs.
• You want to restart the tracker after a crash or update to ensure a clean state.
• You need to test the UI with a specific subset of exercises.
• You want to temporarily disable or re-enable the tracker from scripts or hooks.
• You need to clear Chrome window cache when display or sizing is wrong.

Best practices

• Always kill existing instances before launching to avoid port or resource conflicts.
• Use VIBEREPS_EXERCISES to create focused tests (e.g., only squats or jumping jacks).
• Set VIBEREPS_DISABLED=1 in hooks when you need to pause the tracker without removing configuration.
• Check the tracker port (e.g., lsof -i :8765) to confirm it stopped or started successfully.
• Remove /tmp/vibereps-chrome if the window size or rendering looks incorrect.

Example use cases

• Launch the tracker in quick mode during a larger automated workflow: kill any running instance then run exercise_tracker.py user_prompt_submit '{}'.
• Run the tracker in normal mode after a long task: kill existing process then start exercise_tracker.py task_complete '{}'.
• Test UI with a specific set of exercises: VIBEREPS_EXERCISES=squats,jumping_jacks ./exercise_tracker.py user_prompt_submit '{}'.
• Temporarily disable the tracker from a CI hook: VIBEREPS_DISABLED=1 ./exercise_tracker.py ...
• Fix UI sizing before a demo by clearing Chrome cache: rm -rf /tmp/vibereps-chrome and restart the tracker.