Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/file-watcher
Configure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.
Passed 21 of 21 test cases with the skill, and 11 of 21 without it.
and 9 more in the full report
10 fixed12 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Claude Code's file watcher system implementation, what is the standard file stability threshold duration in milliseconds before a change event is emitted?
| Checked | Without skill | With skill |
|---|---|---|
| The threshold duration specified is 500ms. | Missed | Passed |
The instructions your model reads when the skill loads.
Use Claude Code's FileChanged and CwdChanged hooks to create reactive workflows that respond to file system changes.
Use when:
Claude Code's SessionStart and CwdChanged hooks support returning watchPaths to register file watchers. The current cwd-changed.js script focuses on env injection; to add watch registration, your hook script must output this JSON structure:
{
"hookSpecificOutput": {
"hookEventName": "SessionStart",
"watchPaths": [
"/absolute/path/to/.env",
"/absolute/path/to/package.json"
]
}
}
When watched files change, the FileChanged hook fires with:
{
"hook_event_name": "FileChanged",
"file_path": "/path/to/changed/file",
"event": "change"
}
CwdChanged and FileChanged hooks can write to CLAUDE_ENV_FILE to inject environment variables into subsequent Bash commands:
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.