grepai-watch-daemon

Watches project files and updates code indices via CLI daemon commands.

18|2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-watch-daemon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grepai-watch-daemon
Source: https://github.com/yoanbernabeu/grepai-skills/tree/main/skills/indexing/grepai-watch-daemon
Command: npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-watch-daemon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the maintenance of up-to-date code indices by continuously monitoring a project for changes and updating embeddings accordingly.

Core Features & Use Cases

  • Real-time file watching to trigger incremental indexing.
  • Foreground and background daemon management, with status checks.
  • Use cases include initial indexing for new projects, ongoing monitoring in active repos, and multi-project workspaces.

Quick Start

Start watching a project with: grepai watch Check status with: grepai watch --status Stop the daemon with: grepai watch --stop

Frequently Asked Questions about grepai-watch-daemon

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

FAQPage Schema
How do I automate real-time code indexing for my project?

Automate real-time code indexing by running a watch daemon that continuously monitors your project for file changes and updates embeddings incrementally. You can start the process using standard CLI commands in either foreground or background mode.

What is the best way to monitor a multi-project workspace for code changes?

Monitoring a multi-project workspace is handled by the watch daemon, which supports ongoing indexing across multiple directories. It tracks file modifications and automatically updates the codebase indices without requiring manual re-indexing.

How do I check the status of a background indexing daemon?

Check the background indexing daemon status by running the specific status check CLI command. This reports the current lifecycle state and progress of the real-time code indexing process.

Can I manage the lifecycle of a code indexing daemon from the CLI?

You can fully manage the daemon lifecycle from the CLI using standard commands to start, check status, and stop the process. This allows seamless control over both foreground and background indexing operations.

Why do I need incremental indexing for my codebase?

Incremental indexing is needed to maintain up-to-date code indices efficiently, as it updates embeddings only for changed files rather than reprocessing the entire project. This saves time and computing resources in active repositories.