How I Automated Python Documentation Using AST Parsing and Multi-Provider LLMs

We've all been there. You just spent three intense days crafting a highly optimized, beautifully architected new feature. The code is elegant. The tests are passing. The linter is perfectly silent. You push your branch, open a Pull Request, and then reality hits you like a truck: "Oh right. I need to update the documentation." Let’s be honest: writing documentation is the chore that developers love to hate. In an ideal world, documentation evolves alongside the code. In reality, it stays stuck in 2023, while your application code races toward 2025. For the longest time, the solution has been either drudgery (doing it manually) or using brittle, regex-based parsers that break the moment you introduce a slightly complex Python decorator or a nested asynchronous function. I decided I was done with both options. So, I spent the last few weeks building AutoDocGen ( pypiautodocgen on PyPI). Instead of searching for strings like a glorified grep command, AutoDocGen parses your Python code int