You can most certainly write tooling that auto-detects the usage of
the add_filter calls and generates some kind of documentation for
it. You can look at "writing a handler" article for some tips:
http://yardoc.org/guides/extending-yard/writing-handlers.html
Note that since publication, the "Legacy" mode is all but gone-- the
article describes the current state of the art. You can use a
handler + some code object creation (either a method, class, or even
a custom object) to generate seamless documentation for those
blocks.
You can even just use the handlers described above to generate a .md
file or some database of your choosing that you then turn into some
automated documentation on your own. In other words, every time you
parse that block, you can write "Filter: X -- does Y and Z" into a
file that then gets inserted as an extra file (.md). YARD is
flexible in that way. You don't *have* to use the template
generation portion for every customization.
Hope that helps,
Loren