Hail

You can retroactively generate MADR architectural decision records from existing codebases, analyze git commit history and diffs to reverse-engineer design rationale, add decision tags to code, and annotate functions or classes with ADR references across full repos or specific modules.

It targets software engineers, architects, and technical leads maintaining existing codebases, plus teams onboarding new developers who need historical decision context. It suits anyone asking why a codebase looks the way it does or needing to document undocumented architectural choices.

Point it at a full repository or a specific module or folder. It analyzes git commit history and diffs to infer architectural decisions, then produces MADR-formatted Markdown records and can annotate code with ADR reference tags linking implementation to documented rationale.

It requires an existing codebase with git commit history, since decisions are inferred from commits and diffs. You can scope analysis to the entire repository or narrow it to specific modules or folders for targeted decision documentation.

Trigger it when documenting architectural decisions for an existing codebase, generating ADRs from git history, answering why code was built a certain way, or onboarding developers by surfacing historical decisions. Keywords include ADR, architectural decisions, and decision records.