Is your feature request related to a problem? Please describe.

Just realized that docs can have legacy text too, so why stop at Python?

Describe the solution you'd like

Support other comment prefixes (not the YORE word but the actual characters to denote comments).

• Markdown, HTML: <!-- ... -->
• CSS: /* ... */
• TOML, YAML, Ruby, shell: same (# ...)
• Jinja: {# ... #}
• Javascript/Typescript/C/C++/C#: // ...
• what else? (please comment)

Looks like we can go with (comment_prefix, comment_suffix) tuples in a file extension mapping 🤔

Describe alternatives you've considered

/

Additional context

Since we wanted to support dependencies in #3, we would have to find a way to support other ecosystems 🤔 Maybe we could infer the ecosystem based on the extension of the file the comment was found in. For example, a comment found in a *.py file will target the Python ecosystem.