cqs-watch

A task to watch the CPU and GPU temperatures of your computer.

13|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/jamie8johnson/cqs --skill cqs-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cqs-watch
Source: https://github.com/jamie8johnson/cqs/tree/main/.claude/skills/cqs-watch
Command: npx skills add https://github.com/jamie8johnson/cqs --skill cqs-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps your code search index up-to-date by automatically re-indexing when source files change, reducing stale results.

Core Features & Use Cases

  • Incremental re-indexing: only changed files are processed to minimize wait times.
  • File watching: monitors the project directory recursively for changes in real time.
  • Safe defaults: respects .gitignore by default and can be configured with a debouncing window.
  • Use Case: during active development, run cqs watch to ensure search results reflect the latest code edits.

Quick Start

Start the cqs watch mode to automatically refresh the index as files change.

Frequently Asked Questions about cqs-watch

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

FAQPage Schema
How do I automatically re-index my code search when files change?

You can automatically re-index your code search by running a file watching process that monitors your project directory recursively and triggers incremental re-indexing as source files are modified, keeping search results current during active development.

What is incremental re-indexing and how does it reduce wait times?

Incremental re-indexing is a process that only processes changed files rather than rebuilding the entire index. By detecting specific file modifications in real time, it minimizes wait times and reduces stale search results during active development.

Can I configure a debounce window for file watching to avoid rapid re-indexing?

Yes, you can configure a debounce window for file watching using an optional flag. Debouncing prevents rapid successive re-indexing by waiting for a specified period of inactivity after file changes before triggering the update.

Does the file watcher respect .gitignore by default?

Yes, the file watcher respects .gitignore by default, ensuring that ignored files and directories are excluded from monitoring and indexing. You can override this behavior using a specific flag if you need to include ignored files.

What are the limitations of using a file watcher for code indexing?

Limitations of using a file watcher for code indexing include potential performance overhead on very large projects and the need to manage debouncing to prevent excessive re-indexing. It is designed for active development contexts rather than one-time indexing tasks.