skills.rest
alatyshau
alatyshauCOMMUNITY
Explore all skills by this author →
GitHub

commit

Generate a commit message for all workspace changes without committing.

Updated Nov 21, 2025
Search Tags:#git#version control#developer workflow#code changes#commit message#git diff
One-click install
npx skills add https://github.com/alatyshau/duet --skill commit-alatyshau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/tools/commit
Command: npx skills add https://github.com/alatyshau/duet --skill commit-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent commit messages is tedious and often skipped, leading to vague history like "fix stuff" or "update". This Skill analyzes all workspace changes and drafts a well-structured commit message, while never committing on its own. ## Core Features & Use Cases - Full workspace analysis: Runs git status, git diff, and git log in parallel to understand staged, unstaged, and untracked changes plus recent commit style. - Structured message drafting: Identifies the single most important change as the first line (max 70 chars, lowercase English) and lists supporting changes as bullet points. - Split detection: Flags when changes span unrelated concerns and proposes splitting them into separate commits. - Use Case: After a long coding session touching multiple files, trigger the skill to get a concise summary of what changed and a ready-to-use commit message, then decide yourself when to commit. ## Quick Start Ask the assistant to generate a commit message for all current workspace changes using the commit skill.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a commit message from git changes automatically?▼

Run git status, git diff HEAD, and git log in parallel to gather context, then identify the main change for the first line and list supporting changes as bullets. This Skill automates that analysis and presents a ready-to-use message.

How to write a good git commit message for multiple changes?▼

Put the single most important change on the first line in under 70 characters, then list supporting changes as bullet points. If changes span unrelated concerns, consider splitting them into separate commits.

Does this Skill commit changes automatically?▼

No. The Skill only analyzes workspace changes and presents a drafted commit message. It never runs git add or git commit, so you stay in full control of when and what gets committed.

Can it handle unstaged and untracked files in git?▼

Yes. The Skill scopes all workspace changes including staged, unstaged, and untracked files by default, using git status --short and git diff HEAD to capture the complete picture without cherry-picking.

What happens when changes are unrelated in one commit?▼

The Skill flags when changes span unrelated concerns and proposes splitting them into separate commits. It does not insist on the split, leaving the final decision to you.

Related Skills

Explore More Software Engineering Skills→
CristoVenturesCristoVentures
2

git-history-analyzer

Trace file evolution and contributor activity from git history.

Official
Advanced
eriknovakeriknovak

commit-pr

Create a conventional commit, push the branch, and open a GitHub pull request.

Community
Advanced
hojinzshojinzs
16

commit

Enforce one-issue-per-commit with conventional commit formats and passing tests.

Community
Intermediate
JiangAustinJiangAustin

chinese-commit-conventions

Standardize Chinese Git commit messages with commitlint, husky, and commitizen.

Community
Intermediate