Codebase Captain

App "logs in" with an user-provided Bob key & accepts a repository path as input (either local or external), generes a summary consisting of a classification label for the repo, an overview, list of main features, main requirements & uncertainty notes (what is lacking, what makes it hard to scale). After the overview is confirmed by the user (who can also edit the overview output), it will be used to inform next steps, which are the following: -User will have the option to generate an App Map; this is the repository's filesystem with both a brief and broad summaries on every item there (such as folders & files), which makes an onboarding process for a codebase a lot faster and higher-quality. This is generated by static analysis due to the immense cost of tokens that would entail, but users can ask Bob to give a summary of an specific item if they wish to do so. -Frequency Analysis option, which identifies which files are imported the most across the app & lists them sorted by import frequency, also discerning internal files from 3rd party ones. There is also a 'Git Story' feature which shows which commits from the selected repository have the biggest concentration of changes. -Git Story, which identifies commits in the current branch that concentrate more changes than average. -Naval Band which spins up the app from the repository. Can be used with 3rd party testers such as OWASP ZAP to generate further reports. -M-API, which identifies exposed routes & generates documentation. -Test Tester, which lists test files and provides judgement on them based on testing good practices such as coverage, idempotency, etc. -Codebase Debrief, which lists implementation files and judges them based on good practices such as the 12 Factor Methodology. -User also has access to Bob's messages directly if anything looks strange and the user needs to check the AI's reasoning directly. App is all about providing open information. -User can change app theme & language in settings.