lets-commit

Generate Git commit messages from repository context and conventions.

3|Updated May 28, 2026

Search Tags:#git #version control #commit messages #commit automation #commit structuring

Ready to run

npx skills add https://github.com/williamzelesny/lets-engineer --skill lets-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lets-commit
Source: https://github.com/williamzelesny/lets-engineer/tree/main/plugins/lets-engineer/skills/lets-commit
Command: npx skills add https://github.com/williamzelesny/lets-engineer --skill lets-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of creating clear, concise, and structured Git commit messages, ensuring that every commit communicates its value effectively and follows repository conventions.

Core Features & Use Cases

Automated Commit Message Generation: Based on predefined conventions and patterns, it generates commit messages that follow repository guidelines.
Contextual Data Incorporation: Utilizes contextual information like git status, working tree diff, branch name, and recent commits to inform the commit message.
Feature and Bug Commit Classification: Identifies the correct commit type (feat, fix, refactor, etc.) and scopes based on the commit content.
Multi-commit Support: Allows for staging and committing logically separated changes into distinct commits if needed.

Quick Start

/lets-commit

Frequently Asked Questions about lets-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate git commit messages to follow repository conventions?▼

You can automate git commit messages by parsing contextual repository data like working tree diffs, git status, and branch names to generate structured messages. This process determines commit types and scopes based on content, ensuring every commit follows repository conventions and communicates value effectively.

What is the best way to structure git commits for features and bug fixes?▼

Structuring git commits for features and bug fixes requires classifying the commit type and scope based on the content changes. By analyzing the working tree diff and applying predefined conventions, you can automatically categorize commits as feat, fix, or refactor to communicate value clearly.

Can I stage and commit logically separated changes into multiple distinct commits?▼

Yes, you can stage and commit logically separated changes into multiple distinct commits. This multi-commit support allows you to break down mixed changes in your working tree, ensuring each commit represents a single logical update that follows structured message conventions.

Does automated commit message generation work with existing repository conventions?▼

Automated commit message generation works with existing repository conventions by incorporating contextual data and predefined patterns. It analyzes your recent commits, branch names, and working tree diffs to ensure the generated messages align with your established version control workflows.

What contextual data is needed to generate structured git commit messages?▼

Generating structured git commit messages requires contextual data including git status, working tree diffs, branch names, and recent commit history. This repository data informs the classification of commit types and scopes to ensure the generated messages follow project conventions.