Can I use DevSkim to detect and flag based not on file content but file name, file extension, existence or other file metadata?

I am wondering if I can flag files based on file name or extension? And preferably in combination with other files. Example use-case:

The scan folder contains an '.exe' file. I want to flag that exe file with the warning that pre-build files should not be part of the repository as it makes it harder to audit and verify the source code.

Preferably in combination with other files or folders. Such as, only flag the .exe file when the scan directory also contains a .git folder (not unlikely and indicating it's a git repo).

Or flag any blob for that matter. Perhaps files without file extension.

Or on any other metadata like, binaries unsinged by a trusted certificate etc.

The issue names no files, tests, or entry points. Start by locating DevSkim's rule and scanning entry points, then determine whether rules can inspect filenames, extensions, neighboring files, and metadata. Done should include a defined way to flag the requested .exe and repository-context cases, with behavior for unsupported metadata clarified.