watch

You can monitor file changes by starting a watch daemon with a set poll interval, letting it scan for edits, and automatically routing actionable insights to appropriate skills or intake queues without manual triggering.

Git-diff based change detection identifies modified files by comparing repository states, routing those changes and inline marker actions to appropriate skills. It falls back to timestamp-based detection when git is unavailable to ensure reliable operation.

Yes, you can route inline marker comments, such as @citadel: markers, to the appropriate skill. The system parses these markers during file scans and dispatches the specified actions automatically.

Unmarked file changes are automatically queued as intake items for automated processing. The system uses stateful intake tracking to capture unrecognized edits and route them into an intake queue for later review.

Yes, file change detection works without git by falling back to timestamp-based detection. This ensures reliable monitoring and dispatch of file changes even when git is unavailable in your project environment.

Batched dispatch limits automated actions to a maximum of five per scan to prevent overload when monitoring frequent file edits. This constraint ensures stable routing of marker actions and intake generation across tests, docs, and source files.