/watch
Set up a file watcher that triggers Claude on file changes
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/watch
Context preview
What this command does when you run it.
Set up a file watcher that triggers Claude on file changes
Command definition
watch.mddescription: Set up a file watcher that triggers Claude on file changes
argument: Watch path (file or directory)
File Watcher Setup
Set up a chokidar-based file watcher for: `$ARGUMENTS`
Instructions
1. Ask the user the following questions interactively (use AskUserQuestion):
- **Prompt**: "What Claude prompt should run when files change?" (remind them they can use `{{file}}` as a placeholder for the changed file path)
- **Glob filter** (optional): "Do you want to filter by file type?" with options like `*.tsx`, `*.ts`, `*.css`, or no filter
- **Debounce delay** (optional): "How long to wait after the last change before triggering?" with options 200ms, 500ms (default), 1000ms
2. Verify the watch path `$ARGUMENTS` exists. If it doesn't, warn the user and ask if they want to proceed anyway.
3. Ensure `scripts/watch-files.mjs` exists. If not, inform the user it needs to be created (it should already exist as part of the file-watcher skill).
4. Ensure `chokidar` is in devDependencies. If not, run `bun add -d chokidar`.
5. Ensure `package.json` has the `watch:files` script. If not, add it:
"watch:files": "node scripts/watch-files.mjs"
6. Run a smoke test:
- Start the watcher in the background with the user's chosen options
- Touch a file in the watched path
- Verify the watcher detects the change (check its stdout for the log line)
- Kill the background watcher
7. Print the final command the user can run:
node scripts/watch-files.mjs <path> '<prompt>' [--glob '<pattern>'] [--debounce <ms>]
Skill Reference
See `.claude/skills/file-watcher/SKILL.md` for full documentation, examples, and troubleshooting.
Read more
description: Set up a file watcher that triggers Claude on file changes argument: Watch path (file or directory)
File Watcher Setup
Set up a chokidar-based file watcher for: `$ARGUMENTS`
Instructions
1. Ask the user the following questions interactively (use AskUserQuestion):
- **Prompt**: "What Claude prompt should run when files change?" (remind them they can use `{{file}}` as a placeholder for the changed file path)
- **Glob filter** (optional): "Do you want to filter by file type?" with options like `*.tsx`, `*.ts`, `*.css`, or no filter
- **Debounce delay** (optional): "How long to wait after the last change before triggering?" with options 200ms, 500ms (default), 1000ms
2. Verify the watch path `$ARGUMENTS` exists. If it doesn't, warn the user and ask if they want to proceed anyway.
3. Ensure `scripts/watch-files.mjs` exists. If not, inform the user it needs to be created (it should already exist as part of the file-watcher skill).
4. Ensure `chokidar` is in devDependencies. If not, run `bun add -d chokidar`.
5. Ensure `package.json` has the `watch:files` script. If not, add it:
"watch:files": "node scripts/watch-files.mjs"
6. Run a smoke test:
- Start the watcher in the background with the user's chosen options
- Touch a file in the watched path
- Verify the watcher detects the change (check its stdout for the log line)
- Kill the background watcher
7. Print the final command the user can run:
node scripts/watch-files.mjs <path> '<prompt>' [--glob '<pattern>'] [--debounce <ms>]
Skill Reference
See `.claude/skills/file-watcher/SKILL.md` for full documentation, examples, and troubleshooting.
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command

