dev-swarm-draft-commit-message

To generate conventional commit messages from git diff output, you analyze the staged code changes to determine the commit type, scope, and summary. This ensures your git history follows a standardized, imperative mood format like `feat(auth): implement user login endpoint`.

An atomic commit in version control bundles a single, focused task such as a feature, fix, refactor, or documentation update. Enforcing single-task commits creates a cleaner, more informative git history that simplifies code review and project maintenance.

Formatting a git commit message to follow the Conventional Commits specification requires structuring it as `type(scope): summary`. You must analyze your code changes, identify the specific modification type and scope, and write a concise summary in the imperative mood.

Yes, you can automate commit message drafting for features, fixes, refactors, and documentation updates. By analyzing the git diff output, the automation determines the appropriate type and scope for each change, ensuring standardized conventional commit messages across different tasks.

No, drafting conventional commits does not require analyzing the entire repository history. It focuses on analyzing the current git diff output to accurately summarize the staged code changes, determining the specific type, scope, and summary for the immediate commit.

A conventional commit summary must be written in the imperative mood and adhere to specific length constraints. By analyzing the actual code changes, you ensure the summary remains concise while accurately reflecting the single-task modification.