I've found a great article by G-J van Rooyen where he suggests two prompts for the case when you inherit an old codebase and need to quickly understand the flaws and the backstory of main code decisions.
The full article explains a lot in details, but I've just tried to run these two prompts.
Prompt 1 - REPORT.md:
We must do a review of the current repo. Analyze the code and write a report (REPORT.md) that gives information on:
- The structure of the repository
- Its overall purpose and functionality
- Coding conventions
- Code quality / "Code smells"
- Potential issues
Here are a few screenshots of the result REPORT.md on one of my semi-old Laravel/Livewire/Filament project:
Prompt 2 - HISTORY.md:
Create a HISTORY.md file that tells the story about this app's development, progress, and crises, as revealed by the git commit history and branches.
As part of the result, you have the timeline in a clear table in HISTORY.md:
But also, the whole file result is hilarious. It reads almost like a detective story. Here's one excerpt:
