It seems fairly straightforward to me (albeit filling in some inferred gaps): it runs configured commands when $CWD changes to a matching path/pattern.

Writing high quality docs is a challenging task, and one which many people—even if they’re quite good at it—will understandably prioritize lower than a first implementation effort as they validate idea. Which doesn’t necessarily mean that you’ll be impressed by the thing in it’s current state, but you certainly don’t need to call someone’s project garbage just because you’re not interested in it.

You could just… move on to something you’re more interested in. Or you could ask a question clarifying what the thing is/does. Or you could even offer constructive feedback like ‘the current README doesn’t make it clear to me what this does, a demo and a clearer explanation might help’. You even almost did that. But you undercut that message, needlessly insulting the project and potentially discouraging the human who made the effort to create it. That benefits no one.