DandyLyons

5 ms·

1. 1.▲
   by DandyLyons 3mo ago

   Starred
2. 2.▲
   by DandyLyons 3mo ago

   Idk. I did make some edits right after posting (just rewording stuff). Maybe the forum didn't like that?
3. 3.▲
   by DandyLyons 3mo ago

   treedocs already has the ability to read multiple treedocs.yaml files. (I should probably document this better.) treedocs.yaml files can be "nested". So you would have one at the top of your repo, and then you could optionally hav
4. 4.▲
   by DandyLyons 3mo ago

   In practice, the LLM, treedocs and I all work together to maintain it. treedocs finds missing and extra paths, and missing descriptions. The LLM writes descriptions. git makes sure I never forget to run treedocs sync. And I always have the
5. 5.▲
   by DandyLyons 3mo ago

   I only have a Mac to test on, but I am open to releasing on Linux or Windows if someone would help.
6. 6.▲
   by DandyLyons 3mo ago

   It definitely feels more correct from a first principles perspective. It always seemed crazy that we often just throw a bunch of data at an LLM and go figure it out. It's filled with irrelevant junk. That would slow us down so why woul
7. 7.▲
   Show HN: Treedocs: Documentation that automatically checks for staleness(dandylyons.github.io)

   53 points by DandyLyons 3mo ago|19 comments
8. 8.▲
   by DandyLyons 3mo ago

   Hi HN, I built treedocs, a CLI that shows a tree of your file structure, side-by-side with docs. The idea is simple: your filesystem already tells you what exists, but not what each path is for. treedocs mirrors the file tree into a treedoc