git-commit

Conventional commits enforce a structured format: a type (feat, fix, etc.), optional scope, and description under 52 characters, with body text wrapped at 72 characters. This Skill automates the process by grouping your session-modified changes and generating commits that follow this standard, improving code review traceability.

Atomic commits group logically related changes by feature or module into single, focused commits rather than bundling unrelated work. This Skill identifies your modified files, organizes them by feature or fix, and commits each group separately with conventional-commit messages, making history cleaner and easier to review.

Yes. This Skill automates conventional-commit creation by enforcing type definitions, subject and body length constraints, and consistent formatting rules across all commits. It delegates the workflow orchestration to a subagent and outputs a final git log summary, eliminating manual formatting inconsistencies.

This Skill operates on session-modified files only, identifying what you changed during your current work. It stages and commits those files in logical groups by feature or module, applying conventional-commit formatting to each group and leaving uncommitted changes untouched.

This Skill enforces conventional-commit constraints: subject lines must be 52 characters or fewer, and body text wraps at 72 characters. If your message would exceed these limits, the Skill reformats it to comply, ensuring your commits meet standard conventions without manual editing.