are-discover

Codebase file discovery involves using automated tools to enumerate your directory structure and identify all relevant file locations for targeted documentation workflows. This process supports auditing and maintenance tasks by mapping files quickly.

Yes, you can monitor long-running file discovery tasks through real-time progress polling. The discovery process runs in the background and outputs progress logs, allowing you to track the status of scoped operations across your codebase.

You can exclude specific files from codebase analysis through exclusion planning, which allows you to review and propose patterns to omit from future runs. This enables targeted documentation workflows by scoping your discovery operations.

Scoped discovery is the process of targeting specific files and locations within a codebase rather than scanning everything indiscriminately. You need it for codebase auditing when you want to focus your documentation workflows on relevant Phase 1 assets.

Yes, automated codebase discovery reads the version from the .claude/ARE-VERSION file. This version file is required to initiate the background discovery process and ensure compatibility with the targeted documentation workflows.

The best way to map directory structure for targeted analysis is using automated file discovery that supports scoped operations and exclusion planning. This approach outputs a findings summary while running in the background to handle large codebases efficiently.