abd-commit-msg

Generate meaningful commit messages by analyzing git status and diff to determine behavior, then formatting output as a concise, present-tense message summarizing what changed and why. It infers scope from changed files and conversation context to document intent clearly.

Automate commit message formatting by triggering the commit workflow when file changes occur, inferring scope from last_commit_scope.json or scope.json, and enforcing formatting rules for present-tense messages that improve traceability and collaboration across version control workflows.

Yes, this commit message generator supports both automatic and manual commits. When you trigger a commit request, it uses git status and diff to determine behavior changes and formats a concise message reflecting scope and modified files.

Commit messages lack traceability when they fail to reflect scope and changes clearly. This tool solves that by inferring scope from last_commit_scope.json, scope.json, or conversation, then generating present-tense messages documenting what changed and why.

Yes, you can infer commit scope from conversation context when configuration files are unavailable. The tool checks last_commit_scope.json and scope.json first, then falls back to conversation history and changed files to determine scope for the commit message.

Write present-tense commit messages by summarizing current changes into concise output that states what changed and why. The tool analyzes git diff to determine behavior and formats the result as a present-tense message documenting development intent for better collaboration.