reversa-detective

Extracting implicit business knowledge from legacy code involves analyzing Git history and codebase logic to surface historical decisions, domain constraints, and permission models. This process generates structured artifacts like domain.md and ADRs to document the project's rules.

Documenting permissions and state machines in an existing codebase is best achieved by reverse-engineering the code to extract access controls and machine states. This generates dedicated permissions.md and state-machines.md files according to a configurable documentation level.

Git archaeology recovers architecture decision records by tracing historical commits, refactoring notes, and business rationale embedded in repository history. This surfaces past technical decisions and governance logic, enabling safer evolution of legacy software.

You can generate domain documentation for legacy software without explicit comments by analyzing the code's implicit validations, constraints, and logic. This extracts the embedded domain knowledge and produces a comprehensive domain.md artifact.

This approach requires no specific dependencies or components to analyze repository history. It operates directly on your existing codebase and Git commits to identify implicit domain knowledge and generate documentation artifacts.