#Git

Turns a diff into a clear commit message that explains intent rather than restating the changed lines. Useful for keeping a history that is worth reading during an incident, when the question is always why a change was made and not what it touched.

Explains how an unfamiliar repository is organised, what each directory is responsible for, and where to start reading. Genuinely useful when joining a project or evaluating a dependency, since architecture is rarely documented as clearly as the API.

Produces commit messages that follow the Conventional Commits specification, with the right type prefix and a scoped subject line. Keeps a shared history readable and makes automated changelog and semantic-version tooling work properly across a team.